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; } } }

Project Configuration: Workflow gets added to wrong issuetype in workflow scheme

Chris K_4mhp8d

Dear Community,

We have created a uniform workflow for the issue type "Project", which we now want to roll out to the Jira projects that contain this issue type. The workflow should be added to the respective workflow scheme of the project. When testing in my test project, however, I already encounter a strange system behavior: As soon as I add the workflow to the "Project" issue type by clicking on "Finish", it is assigned (without an error message) to the "Subtask" (German: "Unteraufgabe") issue type (see screenshot below):

2023-06-12 09_55_40-Project Application Management Collaboration Tools - Workflows - Jira.png

I can't explain the system behavior at this point...

Am I missing something here?

Accepted answers

Radek Dostál

If you're editing this from the project - try doing it from Workflow Schemes administration page instead. The project side scheme editor can sometimes be a little funky, I think I came across this at some point and going through workflow schemes helped, but it was.. maybe a few cases, not sure if it will work for you too but worth a shot.