nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unassigned Issue Types

Michael Parker_g3xsan

I need some help please.

I have a work flow scheme where I want an issue not to follow a desired work flow. I have removed this issue and added the issue I want to pass via this workflow.

But as the Unassigned Issue Types is defaulted to the workflow scheme this is not allowing me to remove this.

Please can anyone help?

Accepted answers

All comments

Joe Pitt

The basic answer is, if you are forcing different issues to follow different paths there is a condition on the workflow. You need to find out what it is. It sounds like unassigned issues can't follow the path you want.

Michael Parker_g3xsan

This dont work basically I want the issue dev bug to be visible when creating a new issue.

But I dont want this to follow the workflow my project has.

Joe Pitt

Your first post says unassigned. Now you're saying dev bug, which isn't the same. If you want a different issue type to follow a different workflow you need to assign that issue type to a different workflow in the workflow scheme.

Michael Parker_g3xsan

Hi Joe

Thanks for this.

I want the dev bug to remain as an issue type when raising sub tasks so when creating a new issue.

And when these are created, I dont want this to follow the current workflow set up with my project.

If I allocate the dev bug to another workflow would this still let me use is when creating new issues?