Workflow missing in column management?

[Markus]

I added a new workflow for one issuetype to our project. The other issuetypes still have the old workflow.

But if i create a new board in this project and go to the column management under board configuaration im only able to see the statuses from the new workflow. The old statuses are completely missing. They dont show up in the column "Unmapped statuses" either. 

If i go to the project configuration im able to see that the workflows are assigned correctly to the issuetyes. The board filter is also using the standard "project = XXXX" and nothing else. 

If i create a issuetype that has the old workflow assigned to it, i logically cant see it on the board. But if i go to the "issues" tab on the left sidbear it shows up there with the correct statuses from the old workflow assigned to it.

Is this a bug? Is there something wrong with my workflow?

[Jack Brickey]

@Markus, so here is what I gather from above:

1. you have a project w/ multiple issuetype
2. more than one workflow covers the issuetypes and all WFs are published
3. you have a board w/ only project = xxx, where xxx refers to the project in question
4. if you create issues of each issuetype they are correctly created with the appropriate WF. HOWEVER...
5. the board only displays issue with from one of the WFs

So, if all above is in fact thru then that would be a bug I think but before seeking Atlassian support I would check the following:

• verify #3 - recheck the filter AND Sub-filter (if it exists) for the board to ensure the non-displayed issuetype are not excluded
• check if there are any quick filters that would hide issues
• from the edit issue view check the workflow of one of each issuetypes to verify they are as expected
• is there a default board associated w/ the project? if so what is displayed there?
• can you create another board just to see if it behaves the same way
• In Board Settings > General if you click on the Edit Filter Query what issues are displayed? If the filter indeed is project = xxx only and only certain issuetypes are displayed when you can demonstrate others are clearly open then that would be bug.

Are you using server or cloud and if server which version?

If everything continues to check out I would open an issue w/ Atlassian to have them investigate. But to be honest I would be a bit surprised if this is associated w/ a bug.

[Markus]

Hi,

1. The filter is "project = projectname ORDER BY Rank ASC" and i removed the sub-filter
2. Sadly no
3. Yes they are correct
4. The default board still has the old statuses but it says "The status is not available in any of the workflows..." when you move the mouse on them 
5. I have the problem on all new boards too
6. see 1

The funny thing is that we did exactly the same thing with other projects and it worked fine there. I contaced our Admin maybe he knows whats going on. 

Thanks!

[Deleted user]

Hi - I'm seeing a similar/same issue - I created a new scrum board and in the column management area of the board settings it's only showing the statuses for ONE of the two workflows I have assigned to the project issue types.

I already had some kanban-type boards on this project and they have always detected all status options from all assigned workflows, it's just my new scrum-type board that is having trouble.

Did you get any answers to this issue?

[Deleted user]

Ok I tracked down the cause of my issue - The board filter I had was confusing the column management screen as per https://community.atlassian.com/t5/Jira-questions/Jira-agile-board-columns-incorrectly-saying-statuses-not/qaq-p/838224

I had to tweak the jql in the board filter (no difference in filter result) to trick the settings screen to make the statuses available.

[Danyal Iqbal]

Please share the filter definition with us. You filter does not retrieve any issue with the old workflow.

[Markus]

project = projectname ORDER BY Rank ASC

Do you mean this filter definition?

[Danyal Iqbal]

You might be using the software simplified Workflow. Check the columns tab in board configuration.