Issue types in the issue type dropdown do not match the workflow scheme

[Thayne Munson]

I have a Jira project (ITP) that I use in Advanced Roadmaps that represents 2 hierarchy levels (Si - Strategic Initiative, Cp - Capability) above the Jira Epic level.  When I view the ITP workflow scheme it only includes the Si and Cp issue types which is what I want.  But, when I try to Create a new ITP issue,  the issue type dropdown includes Si and Cp as well as Epic, Story, Task, etc, which seems to conflict with the workflow scheme which only shows Si and Cp.  I am not sure how to remove the Epic/Story/Task issue types from the issue type dropdown. (see attachment below).  Any suggestions?  Thanks. Thayne Munson

[Bharathi · Accepted solution]

Hi @Thayne Munson,

This issue can be fixed by checking the issuetype scheme of ITP project. The issuetype scheme will have all listed issuetypes(in the dropdown) associated with it, which is the reason why they are listed in the create option.

Due to the above, the workflow scheme also associates the workflow to these unassigned types as part of the 1st line in below screenshot.

Hence, all issuetypes except Si & Cp needs to be un-associated from the ITP project's issuetype scheme to fix this issue.

Hope this helps!

Thanks!

[Thayne Munson]

Thank you.  

[Trudy Claspill · Accepted solution]

The Workflow Scheme does not dictate which types of issues can be created in the project. It only determines the workflow for issue created. And by default a Workflow Scheme contains an association of a Workflow to "Unassigned Types". That means if the Workflow Scheme does not include a an association for a specific issue type to a specific workflow, then the workflow designated for "Unassigned Types" will be used.

It is the Issue Types Scheme that determines which issue types will be available to create in that project. As @Mikael Sandberg mentioned, you will need to edit that scheme to remove the issue types that you don't want to allow to be created in the project.

However, if you remove the Epic issue type from that scheme, that might have an impact on your ability to have it as part of your Advanced Roadmap hierarchy. I'm not positive about that because I have not had an opportunity to work with Advanced Roadmaps. If it negatively impacts your Advanced Roadmaps, then you might want to instead put a Validator in the Create Transition in the workflow that says Issue Type can be only Si or Cp. That would block the actual saving of the Epic issue. You can put a Condition on the Create Transition, so you can't proactively prevent the selection of the Epic issue type.

[Mikael Sandberg · Accepted solution]

You can add/remove issue types by going to the issue type scheme that the project is using. Have a look at Associate issue types with projects for more information.