Assume I have some commits like this:
XY-24 commit 3 XY-24 commit 2 XY-24 commit 1
These commits are visible in JIRA (if configured properly with FishEye).
What happens now if I move this issue to another project and thus get a new Issue Key? I know that I can still use the old issue key to find the issue in JIRA, but what happens with the commits? Are they still visible?
(I am curerntly not setup to test this myself. Any help is appreciated.)
I've just tried this myseld with local instances, and it worked for me. These were the steps I've followed:
This was tried using FishEye 2.8.0 and JIRA 4.4.5 and, as far as I can tell, this was not changed in newer versions.
If you face any problems, don't hesitate to create a support issue.
One issue with this seems to be...
We have the following conditions in the workflow against a transition:
User A commits code against ProjectA-123. User A moves ProjectA-123 to a different project. The issue key becomes ProjectB-456. Since the commit is against ProjectA-123, JIRA treats the issue as if it has no commits against ProjectB-456.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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