We have a JIRA-Fisheye-Perforce environment, and everything is working as expected except in the case where users link the Perforce job (created by JIRA) to a changelist *after* the changelist was submitted to Perforce. I understand that the Fisheye polling of new Perforce changelists doesn't catch this, but it doesn't seem to help to manually start a Re-scan Perforce changelists either.
The changesets that were linked to jobs never show up in the JIRA issue!
How do get this info into JIRA?
The JIRA version is 5.1.2
As you already described, FishEye needs to re-index the Perforce changelist.
In the repository maintenance you can re-index the Perforce Changelists, 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).
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hey everyone! My name is Natalie and I'm an editor of the Atlassian Blog and I've got a question for you: What's your favorite quote about teamwork? We've compiled a list here, along with...
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