I have a project and new workflow established. I have associated my workflow schema and new workflow to the project and everything is working fine for the issue type. But, I have noticed that in my Workflow Schema, it still indicates it is inactive. The workflow is Active. How can I fix this where the new workflow schema is Active?
It's not - you've either hit rather a serious bug, or you're misreading the screen.
To establish which it is, read the project config VERY carefully - what *exactly* is the title of the workflow scheme it is using? Now go into the list of workflow schemes and check for exactly that name.
Please bare with me. I am looking at the current project scheme called OurMainScheme. Under that are two workflows - ABC Project workflow and XYZ Project Workflow.
We do have a scheme called XYZ Project (the word scheme was accidentaily left off) which I beieve to be tied to XYZ Project Workflow. On the Administration | Workflow Scheme display that XYX Project scheme is showing inactive but the workflow that we tied to it (XYZ Project Workflow) is there and is also under "OurMainScheme"
I was expecting to see two active schemas under the one project and just one of those schemas having my XYZ Project Workflow under it - which would be the scheme called XYZ Project.
When I go to Adminitration | Workflow. I see my XYZ Project workflow. Under the workschemes column for that, I see two schemes tied to it - OurMainScheme and XYX Project. So, the XYX Project Workflow is tied to two schemes.
If I go back to Administration | Workflow and go to the Switch Schema box and look at the dropdown, I do see XYZ Project schema name available as well as OurMainScheme name available. Could it be possible that the workflow was displayed in Switch Schema instead of a schema and we picked XYX Project Workflow?
Any advise would be appreciated. We are expecting this to be looking differently.
Ok, there's one huge issue with all of that. A project can only have ONE workflow scheme.
So, I don't understand why you're saying "two schemes" when you're looking at a project - that really doesn't happen. I suspect this might be language - you're using workflow scheme to mean something different from Jira's "workflow scheme" usage.
Could you go to the PROJECT and tell us what SINGLE workflow scheme it is using?
If you're not sure what I'm getting at, have a look at the first screenshot on https://confluence.atlassian.com/display/JIRA/Activating+workflow- under "Worfklows", you can see it says "Doco workflow scheme" - there can only ever be one line there - what does that say?
Thanks. Part of this "might" be interpretation of language. We thought there could be mroe than one scheme tied to a project. So the Switch Scheme is truly that - it switches it. The ourmainscheme is what we see. There are two workflows inside of that. What puzzles me is that something hapenned. Our workflow XYZ Project Workflow, which was tied to XYZ project (schema), now seems to be under both schema's the inactive one and the OurMainSchema. That is what is throwing us. So it is tied to both? How could the switch do that?
No, it's one scheme per project.
I'm getting a bit lost on what you're talking about with this. Start with the single workflow scheme you have for the project. It might have many workflows, but you'll find all of them are marked as active.
Inactive workflows are only marked as inactive if you don't have them in a workflow scheme that is in use with a project.
I don't understand what you mean by ownership.
I'd have thought it was obvious that a workflow can be in many schemes, just by the fact that when you create or amend a workflow scheme, it offers you the full list of all available workflows every time.
It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...
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