Is there a way to easily navigate to a Bug in SugarCRM using a URL string?

[BAA Steve]

Hi,

I am trying to find a way to integrate TortoiseHg with SugarCRM 6.0.3 (Build 4339) so our development staff can associate Sugar Bugs with their Mercurial/TortoiseHg check ins.

Most bug tracking systems have a mechanism similar to what Jira provides in the example below to navigate directly to bug JHG-16:

https://studio.plugins.atlassian.com/browse/JHG-16

I’ve tried several methods on our local Sugar server to access the bugs, but the closest thing I can come up with is:

http://mysugarserver/sugarpro/index....er_basic=12345

But this URL still doesn’t take me to the detail page for bug 12345. The user is required to click on a link referencing bug 12345 and then is re-directed to a page with a long URL similar to the one below:

http://mysugarserver/sugarpro/index....-xxxxxxxxxxxxx

Has anyone else run into this problem? If so, how did you solve it?

Ideally I would like to see something like:

http://mysugarserver/sugarpro/index....ugNumber=12345

Thanks in advance,

Steve

[blak3r]

Hey,

I never really tried to switch over from Bugzilla. Got busy with other things.
If you make the plunge, please let me know how it goes!

~blake

[BAA Steve]

Thanks for replying.

At this point I'm trying to find a way to hook into either TortoiseHg or Perforce P4V.

I'm really surprised that no one has done this already. With Git, Mercurial, and Subversion all being open source I would have thought that someone would have encountered this same problem.

I may yet land up trying to figure out how to make this work, but like you I'm being pulled in about 100 directions.

Steve

[blak3r]

I think it's a lot of reasons...

CRM being used by the company as a whole is still kind of at the cutting edge of accepted business practices... It's really only practical for smaller companies to do it right now.
(I'm sure others will disagree with this and say it's the complete opposite however)

I too wish more open source projects played with Sugar a little better. I'm seeing positive signs though.

I just re-glanced at your post. I assumed you were asking a different bug question I had posted. I didn't follow your links don't have time... can you just explain in plain english what your trying to do?
- would the developers include something in the comments of their commit to reference a sugar account...
- would developers use Sugar's internal bug tracking?

[BAA Steve]

Hi,

Thanks for taking the time to read and respond to my note.

The problem I'm trying to solve is fairly straight forward. Most developer tools provide integrations with bug tracking systems by recognizing text a developer types in when writing the description of how they fixed the bug. The developer normally uses the syntax:

# <bug number> at the start of a line.
or
Bug: <number>.

The bug tracking system recognizes the special syntax and automatically turns this into a hyper link that links the fix in the source control system with the bug in the bug tracking system. Some version control systems take things a step further by providing a field in the check in dialog allowing the developer to enter one or more bugs (some even allow the developer to pick from a list of bugs, but that requires deeper integration).

In all cases, the version control systems integrate with the bug tracking system using a simple URL based syntax to create the link between the two systems. The URL must look something like:

http://location_of_your_bug_control_...arameter=nnnnn

Where nnnn is the way to link to the bug. This forum software keeps truncating the URL. Hover over the URL to read the text.

Therefore I would like to find some mechanism that allows me to directly access a particular bug in the Bug Tracker module using a single URL line in a format listed above. The closest I've come is to cause SugarCRM to display a page listing all modules that contain the number nnnnn. The developer must then manually click on the link to get to the bug. The SugarCRM page that comes up always appears even if there is only one choice.

Thanks again for taking the time to review my bug.

Steve

[blak3r]

Here's where i'm getting confused...
It sounds to me like you're trying to create the link in your version control system which is odd to me... I would think you'd want the link in the bug tracker linking to the commit notes in the version control system.

As I understand these systems to work..
User commits... This triggers some type of post commit trigger which finds patterns such as Bug:###.
If any are found, it connect to the Bug Tracking application and add a comment.

You could create something like that fairly easily with a simple webservice script.