Problems with workflow

[jukka peltonen]

I Created new workflow called "Lipe-workflow", using "Diagram" and "text". I add one step more to default workflow.

Only one jira project is using this new "Lipe-workflow", but this creation process changed existing workflow ("ML1.2 workflow") and added this new step also to another jira workflow!!! So now we have the changed workflow in multiple Jira projects (which uses this ML1.2worklow). If i look using "Diagram" this ML1.2workflow I can see the new step there (should not be there), but If I look from "text" I can not see this new step there. It seem to be bug in the "diagram" functionality :(

System tells that the ML1.2Workflow has changed at 17/Mar/14 2:05 PM. (not today when I created the new Lipe-workflow)

What should we do???

Version	6.1.4
Build Number	6159

[Nic Brough -Adaptavist- · Accepted solution]

How did you create "lipe-workflow"? It sounds like you've actually created a draft of ML1.2 and not copied it to a new workflow.

Start with the basics to get this fixed. Look at the list of workflows you have. Then look at the workflow-schemes you have for the projects. There should be a scheme for Lipe projects and another scheme for mL1.2 projects.

(The workflow change date represents your last edit to that workflow)

[jukka peltonen]

hope I managed

[jukka peltonen]

This is now solved :)

[Nic Brough -Adaptavist-]

Would be polite to mark the correct answer as correct. Or, if it wasn't that, then explain what the actual problem was.

[jukka peltonen]

Yes, sorry I don't know how :( to mark

[Nic Brough -Adaptavist-]

Same way you marked your own answer correct - the tick to the left of the avatar.

[jukka peltonen]

Well, I was editing workflow and creating new step and one new status. And I managed to create new workflow, but somehow I managed to change existing status to new (Instead of creating new status) :(

[Nic Brough -Adaptavist-]

I know, it's a bit of a pain. Older versions of Jira didn't have the workflow designer, so it was hard to make this mistake, but the newer versions have enabled you to amend the global lists without realising that they're global. Easy to undo of course, but still a bit of a pain when you're new to hacking workflows.

[jukka peltonen]

Problem solved: "Linked status" (which is global) was changed -> this cause the problem. We changed the status as it was and now works again :)

Lesson was: should be very carefull which parameter is global and which is per project.

[Nic Brough -Adaptavist-]

Ahh, you changed the status, not the workflows. Right.

Generally, watch out for status and screens - as you've found, the workflows refer to these, but they're taken from a global list