Cannot Publish new Workflow in Active Project

[phil borrell]

Hi All,

Here's the problem: I have a workflow where I want to separate out the Sub-tasks to work on a slightly modified workflow, which I know I can do because I have done this on a test project and it works fine. 

But when I apply the workflow changes to the actual project I need it in, and I click publish, Jira goes through the motion of changing the workflow, even asks me which status in the old statuses should match the new ones, I provide the information it's asking for. It then goes through the motions of making the changes, gives me it's % of completion and then tells me it's complete and I can Acknowledge it, but then it hasn't actually made the changes as I go back to the screen where it asks if I want to publish the changes.

The only difference between the Test project and the real project is the number of affected issues. In my test project, there are 4 issues affected, but in my real project, it is close to 1700 issues that are affected.

Question 1, is the 1700 issues in my real project the issue?

Question 2, if it is, how can I fix it?

Question 3, if none of the above, help?

[John Funk]

Hey Phil - Welcome to the Atlassian Community!

It should have still worked, even with 1700 - but there's a good chance that's the problem. 

So first question - then it needs to move to the new workflow, are their statuses that exist in the current sub-task workflow that do not exist in the new workflow. 

[phil borrell]

Hi John, 

Thanks for the response.

So, there is no status' that exist in the sub-task workflow that doesn't already exist in the current workflow, all I have done is reduce the amount of status' in the sub-task workflow from that of the main workflow.

As I said originally, the workflow works in a test project but not in the main project...

[John Funk]

That's a tough one then. I though about moving some of the existing issues to the new status to cut down on the number of records that need to be moved all at once. 

So after you do the publish and it says it is complete. If you then click on the Workflow Scheme, it doesn't show that the new workflow is in there? And there's never any error?

[phil borrell]

So after you do the publish and it says it is complete. If you then click on the Workflow Scheme, it doesn't show that the new workflow is in there? And there's never any error?

It starts the process:

I get the Acknowledgment that it has completed the changes, and then it goes back to the previous screen and asks me if I'd like to publish my changes to the workflow.  please see image: I've checked a few times if it has actually made the changes it says it has, just in case the message is wrong, but then the message isn't wrong at all.

The whole change it goes through does nothing and I am asked if I'd like to 

[John Funk]

Ah, it's because you are using a simplified Workflow Scheme. You will need to create a new Workflow scheme that uses those two workflows.  :-(

Create the workflow first, and then add the two workflows in. And then change the workflow scheme on the project from the current one to the new one you created. 

[phil borrell]

Hi John,

Thanks for the information, that makes a lot of sense.

This now causes a slightly different problem. 

If I attempt to create a New Workflow as you've suggested, I get the Create first status as Backlog, and if I change it to one that makes more sense to the Project, for example, Funnel, then Jira tells me if I make that change it will affect all projects using the Backlog status, this to me, means that the Workflows are still related.

Do I need to create a totally independent workflow with totally different status names and then once it works, i.e., I've assigned it to the Project I want it to be in, re-name the status' to what I want them to be? Which are the names from the original workflow I am having problems with?

If that is the way, it seems a little convoluted?

[John Funk]

Actually, if the Simple one has what you want, I would copy it, give it a new name and then modify the copied one. 

As far as the Backlog is concerned, you could theoretically leave it in the new work flow, but just don't have any transitions going to it. I think what they were referring to is that you don't want to delete the Backlog status out of the system. So you can leave it in the workflow, but have the create go to your Funnel status instead and just let the Backlog status float out there. 

[phil borrell]

Hi John, the workflow works until I try to add a sub-task workflow to separate it from the main workflow, then the same problem occurs.

I think I still need to have a None simplified workflow in play. Interestingly, I cannot find a reference in the Jira documentation that discusses workflows that are not Simplified...

If you have a link for how to create a None Simplified workflow, that would be great?

I tried your other point, creating a new workflow, but the start point is always that same for every project, and if I attempt to change it, Jira tells me it will change for all existing workflows...

[John Funk]

If you are creating a new Workflow from scratch, it will not affect any other workflows. I would ignore that message and keep moving forward with the new one. Just don't delete the Backlog status. 

Can you post of screenshot of the message or what you have in your new workflow so far?

[phil borrell]

Hi John, the first pic is the new Default status

2nd pic is me trying to delete it

3rd pic is me trying to change it

[John Funk]

I would start with the existing Simplified one and just copy that. Then make changes to the copied one. 

I could explain all of the above, but it would be quicker to start with the copy. 

[phil borrell]

Hi John,

I have copied the workflow, I did this before I originally posted the query.

Here's a pic of the original and the copied, the copied works but doesn't have the 1700 issues within it

[John Funk]

By saying the 1700 issues - what project are they on? 

Also, what other issue types do you have on the project other than Sub-tasks?

[phil borrell]

They are on the CloudMove/TechAuto project, and we currently have about 7 different issue types

Story

Bug

Task

Epic

Feature

Risk

Impediment

and Sub-task

Feature, Epic, Risks, Impediment Issue types work from the same workflow but utilise different boards that have some status' turned on and some turned off, and so there is no conflict.

Story, Bug, and Tasks have the same board and therefore the same status' and also have no problem, it is simply the workflow for the Sub-tasks as we do not want them to start in the same place as the Story, and this is the problem

[John Funk]

Okay then - you need to attach the new workflow scheme to the CloudMove/TechAuto project

[phil borrell]

Hi John, i really appreciate your time with this.

So i have attached the new workflow scheme to the CloudMove/TechAuto project, and i get an error.

Please see picture

[John Funk]

You might try doing a re-index first. If you still get the error after that, I would go ahead and submit a support ticket with Atlassian.  :-(

[phil borrell]

Hi John,

Ok, I will.

Thanks for your help with this, I've really appreciated it.

[John Funk]

Sure - sorry I couldn't get you further. Also, please come back and update this post when you get a solution so we can close it out for future reference.  :-)