Workflow Schemes and unassigned and Issue Types

[Lars Sundstrom]

I have created two workflows in my project.

1) Agile workflow with issue types: Epics, Stories, Bugs, Subtasks.

2) Project RAIDD workflow with issue types: Risks, Issues, Assumptions, Dependencies,  Decisions and Action Items

Each workflow has the different issue types assigned to it. 

The issue is that when I add both workflows to the scheme the first workflow by default gets "All Unassigned issue types". And when I then try to publish it tries to apply the flow/states from this workflow to the issue types in the second workflow. 

How to fix?

[Daniel Ebers]

Hi @Lars Sundstrom

from my understanding there are more Issue Types which you have not yet assigned specifically to one of the two workflows in this Scheme.

Therefore Jira "defaults" all Issue Type you have not listed to the B2C: Agile Workflow.

Using "Assign" you can assign further Issue Types to one of the two workflows - this should solve the problem.

Let us know how it goes.

Cheers,
Daniel

[Dirk Ronsmans]

hI @Lars Sundstrom

Do you not have an option on the right side (before you publish) to click an assign or assign to button/link?

you should be able to first assign the workflows to the appropriate issue types before you publish the workflow.

otherwise indeed you try to publish intermediatly it will apply the changes to all.

[Lars Sundstrom]

Not sure I understand but. 

In the example in the picture above. The first workflow "Unassigned Issue Types" gets applied to the second workflow issue types. Not sure how to change that. 

[Lars Sundstrom]

[Dirk Ronsmans]

Hey @Lars Sundstrom ,

I think i was misunderstanding your question at first. I thought you wanted to set the "all assigned issue types" to another flow than the first one.

From what you tell I guess when you apply this configuration, the first workflow (B2C: Agile Workflow) get's assigned to the isssue types listed under B2C RAIDD Workflow?

It almost seems then that it is applying the configuration in steps. When it applies the first workflow it sees those issue types of the 2nd workflow as unassigned (since it's not in the first workflow) so somehow it doesn't see that there will come changes when it applies the rest of the configuration?

If that's the case that seems like a bug and I suggest you open a ticket with Atlassian themselves. (it should do the whole config at once imho). You can open this at https://support.atlassian.com/contact/

Now it could also be that it will first apply it to the issues of the 2nd workflow and then you get the choice to migrate again.. if so that's a hassle but not really broken of course.. still I'd suggest to open a ticket.