Issue linking not working properly after workflow changes

Timo T December 17, 2012

Hi everyone!

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:

clonesTEST-123
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! :)

Tim

1 answer

1 accepted

0 votes
Answer accepted
John Chin
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 17, 2012

Hi Tim,

We have acknowledge this issue as a bug report to Atlassian. Please see JRA-30454 for reference. Make sure you have read every step mentioned in the description. Hope it helps.

Regards,

John Chin

Timo T December 17, 2012

Thank you John, yes it was very helpful.
We had put Fields Required validators to the Create transition and found out that after removing them cloning started to work just fine.

Suggest an answer

Log in or Sign up to answer