How can I restrict certain issue types of a board/project that has a specific workflow?

[cemileertekin]

Context:

We use mainly two types of projects in Jira. For ease, I will refer to them as Type A and Type B. Each of these types have their own workflow and in the creation of the project, we configure the workflow that applies. 

Both Type A and Type B projects have their own unique issue types. These are based on their own unique workflow.

Problem:

I will describe the problem by giving an example. When a user moves an issue from Type A project to Type B project, sometimes they forget to change the issue type of Type A into the fitting issue type of Type B project. Can you follow that? 

As a result, we see now the issue types of both projects mixed up when creating a new issue while this shouldn't be the case. When creating a new issue in Type A project, I only want to see the issue type of the Type A project and the same applies to that of the Type B project. We manually changed issue types of all tickets, but we still see the same problem happening.

Pursued solution:

I want to know how I can configure that when creating a new issue, users can only choose from the issue types that a specific to the type of project that they are in, for example in Type A project a user can only choose from issue types of Type A workflow even if some past tickets might have closed with a mixed workflow. 

The ideal situation would be even that we could restrict users to choose ONLY from the issue types of the workflow of the project that they are moving the issue to. 

Are these two things above possible?

[Ismael Jimoh]

Hi @cemileertekin 

Looking at the description, may I ask why you aren’t using different projects but rather boards?  Make sure project A contains only issue types for board A and do the same for project B.

With different projects, you could have corresponding issue types for each board, when a user moves an issue from project A to B they will need to select the actual issue type available in the other project.

Do correct me if I am missing something here.

Regards.

[cemileertekin]

Hi Ismael, 

Sorry for being not clear enough. With boards, I'm referring to projects. We do have separate projects and define the workflow that fits that project. And within that project we have a board in which we can move issues through the different stages of the workflow. But the problem persists in moving an issue from project A to project B when the workflows are different. 

Best, 

Cemile

[Ismael Jimoh]

Thanks for the clarification.

If I now understand correctly, you have the following scenario:

• You have project A with  Workflow A that is linked to say issue types A and B
• You have another project C with workflow C that is linked to issue type C.
• Earlier in project A, you had some issues that were linked to a different issue type(s) (for example, issue type C which is now considered deprecated) but now, you do not want these issue types to show up when the user is trying to create an issue in project A.

Please can you confirm that I understood you correctly.

If yes, can you also confirm the 2 JQL filters used in each project? And what issue types meet with the 3rd category I described in Project A?

If it is just preventing specific issue types from being selected, I would suggest creating a new issue type (if you have only one, do add deprecated to the name so people know they should not use it), move all issues from the issue type you want to remove to it from the old one from the project. 

• The deprecated visual cue would hopefully help to prevent other users from selecting it.
• Consider moving this issue type to the bottom of your Issue Type Scheme for the project so it appears last.

Unfortunately, this is the only option because provided an issue type is available in a project, the users can select it. Also, the move issue screen cannot be configured/overwritten so all issue types in the project would always be available for selection.

Regards.