We have JIRA, FishEye+Crucible, and Stash installed. Stash is hosting our git repo.
When using smart commits to tie a commit to a JIRA issue, we notice that the Source tab on a issue shows changesets twice: once for Stash and once for FishEye.
This seems to be confusing our users. Also, the order seems to be different. For example, let's say I did 3 commits to a repository. Here is chronological order:
The source tab in JIRA will look like this:
How you recommend I setup the JIRA integration with both products? For the record, I am very new to these products as well, and this is my first time administering.
I agree - this is really annoying. On the one hand, the advice is that Stash and FishEye can live side-by-side. Stash for repository hosting and management and FishEye for code searching and analysis. But on the other hand, there are several problems like this one - viewing a changeset twice on the source tab is redundant and, more importantly, makes it harder to visualize the aggregated history of code changes related to an issue.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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