I see lots of broad statements of "linking JIRA and perforce" but I want to know about actual experience of checking something in, which I haven't been able to find.
A user goes to check in something and they need to put the JIRA issue key in; is there something that suggests what issue to link up (sensibly open issues assigned to said user and possibly recently linked issues)?
We haven't started using Fisheye but suspect we will soon and want to be prepared for it.
As check-ins/commits are made outside of FishEye, directly at repository level, there's no way FishEye can suggest JIRA issues.
The development team must specify the JIRA issue key within the commit message when committing code into the repository.
FishEye only accesses repositories in "read-only" mode in order to index them, and commits get displayed in the web interface after FishEye indexes them.
If this answer was helpful, please allow me to ask you to mark my answer as accepted in order to have it in the top of the thread, also helping other customers.
Thanks in advance!
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot