We have a weird issue with our Fisheye/JIRA/Cruicible setup that we can't work out why it is happening.
We develop on separate 'Story' branches, that then get merged into a 'Feature' branch, then to release merged down onto 'Master'
Sometimes a merge will appear against a JIRA ticket in the Source tab, most often without any files against it in the row. This then makes it impossible to create a Cruicible review against it and our workflow fails as not all the changes against a ticket have been reviewed.
In the case below you can see there are no files listed under the commit message.
Merge branch 'bugfix_ja_portal-581_v1.4.1' into bugfix_v1.4.1
All the other changes against the ticket have the ticket id in the commit message within the source tab. This one doesn't. Should we be doing something different here, like a rebase down before a merge? Or is this a bug within Fisheye when indexing the changes?
FishEye links commits to JIRA issues based on a the commit message. It searches the message via a regular expression looking for characters which look like JIRA keys. It has no relation to the files in the commit/merge. It looks like the merge is being picked up because of the portal-581 part in the message. If commits on the feature branch aren't showing in the source tab that is probably because they don't contain the same JIRA key in their message.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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