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.
We've started renaming our branches a little differently and haven't noticed it again. That wasn't the behaviour I was totally expecting, mainly because we don't normally have to put a commit message in when merging. Makes sense now though, thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David,
We also facing the same issue. Git merge diffs are not available in fisheye. Can you please elaborate your suggested solution?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.