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

how do i associate "Issue Type Screen Scheme" with a project?

Kevin Mote

I've made a new "Create Issue" screen that I want to use for all "Bug" tickets in Project A. (I want Project B to use the Default screen when creating new issues.)

I have...

created and configured the Screen (e.g. "NewBugScreen")
created a Screen Scheme ("CreateBugScreenScheme")
created an Issue Type Screen Scheme ("Create Bug") (and associated this with CreateBugScreenScheme, from step2)
opened Project A admin, Screens tab...

It is in step 4 that I start to lose my way. At one point, I somehow set it up so Project A uses my NewBugScreen for all new Bugs -- but now all my other projects use the NewBugScreen too, which I don't want! I can't seem to figure out how to associate the "Create Bug" Issue Type Screen Scheme exclusively with Project A.

(The screenshot below demonstrates exactly what I'm trying to do.)

Neither the "Configure" nor "Edit" links take you to a screen that allow you to associate a project. (Which is why, in step #4 above, I tried to do it from the Project admin screen. But if the path is there, I couldn't find it.

Accepted answers

Rahul Aich [Nagra]

Here's the link on how to do it. You would need to go into your project as administrator and amend the issue type screen scheme.

https://confluence.atlassian.com/display/JIRA/Associating+Issue+Types+with+Projects

See the section - choosing a project's issue type scheme

A few other points to consider, as you have accidently rolled out the new screen to all your projects.

1. Check that the new screen scheme associates the create issue screen to NewBugScreen

2. The screen scheme is not associated with any other screen used by other projects

3. Check that the issue type screen scheme "create Bug" associates Bugs issue type to the screen scheme CreateBugScreenScheme

Rahul

All comments

Rahul Aich [Nagra]

Here's the link on how to do it. You would need to go into your project as administrator and amend the issue type screen scheme.

https://confluence.atlassian.com/display/JIRA/Associating+Issue+Types+with+Projects

See the section - choosing a project's issue type scheme

A few other points to consider, as you have accidently rolled out the new screen to all your projects.

1. Check that the new screen scheme associates the create issue screen to NewBugScreen

2. The screen scheme is not associated with any other screen used by other projects

3. Check that the issue type screen scheme "create Bug" associates Bugs issue type to the screen scheme CreateBugScreenScheme

Rahul

Kevin Mote

thanks, but unfortunately that is not the answer. (Issue Types != Issue Type Screen Scheme)

Rahul Aich [Nagra]

My bad. the url was incorrect

Here's the right one

https://confluence.atlassian.com/display/JIRA/Associating+Screen+and+Issue+Operation+Mappings+with+an+Issue+Type

btw, did you manage your way through the issue?

Rahul

Kevin Mote

well, I eventually got it to work, but unfortunately, I don't know how! I basically started over, trying to follow the Overview Diagram in reverse: I started from the perspective of the Project and created a Project-specific Issue Type Screen Scheme, and a Project-specific Screen Scheme. Somehow it all just worked this time around!

George Worthing

Frankly I would be embarassed if I'd been the author/developer of the administrative tools that are supposed to enable you to add new screens/screen schemes and issue type screens. This is absolutely the least user obvious design I've ever encountered. Following pages of tutorials and I still can't get a new screen to be properly associated to an issue type on a project.

Kevin Mote

I think I'm finally getting the hang of it now, but I feel your pain. Just grokking the underlying concepts is half the battle. I have found that it is really helpful (during configuration) to carefully name everything precisely (it helps untangle the hairball). So for example, I would name my screen "ProjX Create Screen" or "ProjY Default Screen". Then, to understand how everything connects together, here is an outline that might help:

SCREEN-- Maps fields to a named "screen" (e.g. "ProjA Create Screen" contains the "Description" Field.)

SCREEN SCHEME-- Maps screens to Issue Operations (e.g. The "Create Issue" operation for ProjA will use the "ProjA Create Screen"). Operations are "Create", "Edit", "View" and "Default". The button to associate an Operation with a screen is in the upper-right corner.

ISSUE TYPE SCREEN SCHEME-- Allows you to assign one screen scheme to Bugs and another to Test tickets, for example. (So any given project can have a number of screen schemes; one for each Issue Type, if desired).

Then, to actually ASSIGN an Issue Type Screen Scheme to a particular project (the original question I posted):

Navigate to the Project administration page.
Select the "Screens" tab
Select the "Actions" button in the upper right corner.
Select "Use a different scheme"
The dropdown should list all to the Issue Type Screen Schemes that you have created for any project (again, this is where my precise naming discipline pays off).
Select the one you want, and click Associate.

Andrew Hillson

Thanks Kevin - I appreciate the clarity. This fix worked for me.

Michael Brinson

I agree 100% with George Worthington. The interface is a complete nightmare. Completely non-intuitive.

It also makes me laugh in frustration to read the "helpful" directions on the page that says "This scheme can be used by one or more projects, the field configuration specified for each issue type will be applied to the issues in these projects." but then does nothing to direct you to HOW you go about connecting it with a project. You're left to your own devices to search and search for a solution in the abyss of screen scheme confusion-land on atlassian.com.

Andrew Hillson

I am sympathetic to Michael's complaining/venting. In my experience when multiple users say a feature is confusing and poorly designed its time to take a look at reworking it. Micheal, I recommend reading Kevin Mote's post above ... a few times . By the way, I did get the schemes working but it was not without pain. I appreciate their flexibility and power now.

Art Muir

I have to agree. As PM that is just trying to get the tool set up so I can drive the product forward, I am dismayed that the deeper I get in to this tool, the more I become aware of how convoluted and byzantine the admin tools are. The help pages and community are better than just poking around and trying to guess the intent of the Atlasssian design team, but not by much.

I suspect what would really help is some sort of document that shows the hierarchy of the various Jira elements (project, board, workflow, scheme, etc) and how they control or contain indicators like status, rank, etc.

Steve Jones_l3krj8

Agree with all the frustration comments. Even now 5 years later it's not any better. Surely the brilliant minds that conceived the flexibility and power of JIRA could help simplify it's usage!!!!

(I've administered JIRA for about 3 years but now coming back after a 4 year gap)

Nic Brough -Adaptavist-

In all but the most simple cases, you can have "simple" or "flexible". Pick one.

Atlassian have gone for "flexible". Jira is complex when you are an admin, yes, but if you don't have this complex/flexible thing, you can't make it work for your users (unless they all do everything in one single standard way you can dictate to them, in which case, you should be using a tool which restricts them to that single process, like <name legacy tool here>).

Steve Jones_l3krj8

Rejecting the problem is one approach . However the fact remains that there is a lot of room for improvement in the administration of JIRA projects. I'd be happy to engage in a constructive discussion of ideas to make JIRA more awesome.

mohd zakir_37ldko

Once you have created and configured an issue type screen scheme to your desired settings, you can now associate the scheme with a project. This will apply your chosen screen scheme to each issue type within the selected project.

Choose setting > Projects, and select the relevant project.
Select Screens.
Click the Actions drop-down menu, and choose Use a different scheme:
Select the screen scheme you wish to associate with this project.
Click the Associate button

Thanks

Mohd Zakir

mohdzakirr123@gmail.com

Andrew Keohane

Thank you Mohd! I've been trying to associate the Screen Scheme with the Project for the last 2 hours, following each link I've found and still failing to get the result. This finally worked. I have to agree with the majority view in this thread. After over 20 years experience in relational design, why the Atlassian developers have chosen to structure the system this way is beyond me. Come on guys, please step up and redesign this interface, it's dreadful and ruins a good product.

Steven Wegner

So glad I found this page, I thought I was losing my mind. At least I know now that I am not alone.

Kalindi Pathare

Steven you are certainly not alone on this! It has been 8 hours and counting for me trying to get my head around all this.

Marcus O_Brien_h96mm7

I can say IMO, this whole design is very un-intuitive. Why cant there be a list of fields, and these are associated with a jira issue type, not associated with a screen that couples a issue type and action.

I like most people want to create some fields, tie them to an issue type and project, give the fields some config - mandatory, default value etc. for each project. Then these fields get added to some screens that tie an action and issue type. This would allow us to hide some issue type fields from certain screens.

The current design decouples all items (ie fields, screens, issue type, issue operation) by abstracting another level - the scheme levels. So you can basically do anything with anything, but this is not the use case most of us want, and adds a mind bending amount of confusion. My advice to beat this obfuscation is to draw a nice diagram, do everything in one project at a time (yes I know - lots of wasted effort - but better than breaking everything), and finally test everything in a dummy project first,

Welcome!

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

Quick Links

Find more posts tagged with

jira

issue-type

screen-scheme