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

Creating issue type which will have its own screen/fields

Tim Arthur_pmgph7

This seems like it ought to be straightforward but somehow I cannot get there.

Created new issue type called CR (for Change Request).

Created issue type scheme called Change Request, and it has a sub-task too.

On Issue type schemes page, three dots, associate. Selected the main project which has other issue types of course. Selected "associate". Then, I am viewing step 1 of 8 to MIGRATE other issues now into this CR and Subtask scheme. So, hit cancel.

Searched for answers, not finding any, hope you can help.

Thank you!!!

Accepted answers

Trudy P Claspill

Hello @Tim Arthur

A project can have only one Issue Type Scheme associated to it. If you are trying to associate a different Issue Type Scheme to the project then that association will result in only the issue types from the new scheme being available in the project. All issues of other types have to be converted to issue types in the new scheme.

If you want to just add another issue type to your project while keeping all the original issue types also, then you need to modify the Issue Type Scheme that is already associated to the project and add the new issue type to it.

You'll need to check if that Issue Type Scheme is used by any other project. See how this one says it is shared by 2 project.

Screen Shot 2023-05-05 at 9.30.59 AM.png

If the scheme is shared by multiple projects and you want to affect only one project, then you would need to make a copy of the Issue Type Scheme, modify the copy, and then associate the copy to the desired project.

All comments

Trudy P Claspill

Hello @Tim Arthur

You'll need to check if that Issue Type Scheme is used by any other project. See how this one says it is shared by 2 project.

Screen Shot 2023-05-05 at 9.30.59 AM.png

Himanshi_me2dvl

Hello @Tim Arthur ,

Welcome to Community !

If I understand correctly you wish to create a Issue type with it's own Screen and Fields.

It is not feasible to create an issue type having designated associate screen and fields. You can create screen with designated fields associate it with the screen scheme and can use that screen scheme with the issue type from the project.

From Project settings > Go to Issues >Screens> actions > edit screens > Associate an IssueType with a screen scheme > Select Issue Type and screen scheme and save it

Let me know if this is what you were looking for ?

Have a great day !

Tim Arthur_pmgph7

Thank you. I guess we'll need to live with the fact of four fields useful only for the new issue type, will be present on the fields page for all issue types.

Tim Arthur_pmgph7

Thank you Himanshi for your input.

Trudy P Claspill

No, you don't have to live with that. I'm not sure why you think that is the case.

Perhaps you could explain what you are trying to accomplish in more detail, and then I can offer you advice tailored more to your scenario.

Tim Arthur_pmgph7

That'd be nice, thank you very much @Trudy P Claspill .We'll keep this explanation simple. Issue type of epic, story, bug, sub-task, and cr (for change request).

It is ok if epic, story, bug, sub-task shares common fields, but would like for CR fields to be pared back to only, for instance: CR impact, CR review state, CR decision.

Hope that helps!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud