Hi to all,
I'm trying to change status for the step of the workflow. It works fine, but it affects status of another workflows for the the step, that just has another name.
With other words:
I don't understand why, are they somehow bound together with id's?
How can I handle it ?
Thanks in advance!!!
thanks for your reply!!! I appriciate it, but I'v solved it with another way. You were right, I couldn't update status without affecting another one from different workflow cause workflows were copied.
all my transition and other connection were maintained without changes. And after I just changed status of the step.
I'v checked that status and steps of different workflows has same id, that's why if I'm getting problems. If I'm exporting xml file, both steps has id (6). So I need to finde the way I can change Id of the step, to be able to change linked status without creating any damage to issues that are linked to that workflow
do you copied requirements workflow from general workflow?
1# you create a copy of requirements workflow.
2# create a new step named Invalid and give the in and out transitions including validators,postfunctions,conditions,properties as that of Closed in general workflow.
3# similarly do for other workflows which has same id as 'Closed' which you not require.
the workflows that does not require any change,keep as it is.
5# Now associate the workflow scheme to your project and it will ask while changing the scheme that change Closed to a dropdown which contain Invalid.
select that and confirm.
careful while creating transitions that has exactly as that of Closed.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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