In one project we created a new workflow and new workflow scheme (and permission scheme), swapped all the issues statuses as neccessary and everything works fine. Just one thing - when cloning (or linking) issues that are created after the workflow change everything works fine but when cloning issues that are created before the new workflow/scheme (for example issue TEST-123), a new cloned issue is not being created. What happens is that under the same issue (under Issue Links) appears:
is cloned byTEST-123
It is a messy story but maybe someone could have a clue what could be the possible reason of cloning working this way for issue created before our workflow changes?
We tried with the old workflow/wf scheme and then everything is okay.
Thank you very much! :)
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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