In software the ecosystem if big and it is something common to have to track bugs to thrid party vendors.
Just by adding links to the reported bug may not be enought.
What better solutions do you have for this?
You can assume that the others to do not have Jira but that they do have web based issue tracking systems.
This is possible from JIRA to JIRA -- you can link issues using one-way application links. However, JIRA only has resources to import data from another systems. It doesn't integrate with another bugtrackers by default.
Hence, I've just performed a search in marketplace.atlassian.com checking for plugins for another bugtrackers (I looked for Trac, Bugzilla, FogBugz, Redmine and Mantis), but I didn't found none. So I'm afraid that this is only possible by adding links.
I was not looking for a full integration, more about a simple way of linking to external bugs and be notified when the linked bug (webpage) changes or better when the status is changed. Extractingthe bug status from a web page shouldn't be too hard, or it may even work via RSS - linking RSS feeds ?!
Yep, but if I add a normal link I will not be able to differentiate between normal links and links to RSS or links to other bug trackers.
If I'm not wrong you are suggesting of having a custom link renderer which is able to improve how these links are displayed. Still this would not be able to add a comment or send an email notification when the linked pages is updated.
To implement this it would be another job, maybe a different service that would scan all the links in jira database and ping them.
True. Remote links won't send email notifications when it is updated although you might be able to code that logic also in to your async renderer. Save the old status, see if the new status was changed, send mail and then display - something like that.
But it is best to limit the renderer just for display, for better performance. It is async but still..
Please explain what you mean by tracking dependencies? If there are two issues what do you want to track and how would you like that presented?
A common need is to reflect a remote issue system within JIRA, and to keep the issue updated as the remote system is updated, this is what the JEMH Regexp Field Processor can do with an inbound email generated from a 3rd party system. However, if the two issues live separate lives, that tight coupling may not be desireable...
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs