We have a tricky little situation where we have two different subversion repos's with only one controlling JIRA project.
One repos is the project and the other is the admin site. I understand that we could split the admin site out to it's own JIRA Project, but this is legacy set up stuff and I am trying to avoid confusion for people.
I have set up the two repos in Fisheye, but how do I add two different "Repository paths" within JIRA's Project -> Settings section?
Or should I be looking at this differently?
JIRA is Vs 5.1
Fisheye is Vs 2.7.12
I think the best method to do this would be to upgrade your FishEye to version 2.9 and above. Starting from version 2.9, FishEye only requires the issue key in the commit to detect the issue, and will no longer require a project link. This way, both repos should be able to commit on the project, as long as the commit message contains the issue key
Removing the project mapping in JIRA and FishEye (keeping the Application link, of course) will allow you to see commits containing their project keys from any repository in FishEye.
It is highly recommended you upgrade to the latest version of FishEye however, since huge improvements have been wrt to performance of JIRA/FishEye integration and also some excellent new features such as Inline Issue Creation (from any Crucible comment) and Inline Issue Transition (transition a JIRA issue from within FishEye/Crucible.)
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
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