You can create a link between FishEye changeset and JIRA issue by including JIRA issue ID on your commit comment.
What can you do when you forgot to do this and later want to associate changeset with JIRA issue? We are using subversion, and modifying subverion commit comment to add the issue ID did not help.
If you have an idea, please let us know.
First FishEye needs to re-index that SVN changeset.
In the repository maintenance you can re-index the Subversion Non-Versioned Properties (revprops), specifying a start and end revision.
Alternatively you can trigger this partial re-index from the commandline using "fisheyectl rescan".
The information in FishEye is now updated, but the JIRA-FishEye plugin caches information for performance reasons.
The information that is shown in the Source tab of the JIRA issue is not updated.
If you restart JIRA, the caches are invalidated, and the correct information shows up.
Re-starting JIRA is a brute force approach, there luckily is a gentler approach.
You can request a cache flush through the JIRA UI, as described in Troubleshooting FishEye for JIRA - Updating a Changeset Message (SVN only).
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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