Screen scheme issue

[Jessica Huebner]

I recently created a new project with all new screen schemes. When I go into screens, I can see that one of my screens is associated with two types of screen schemes, when it should only be associated with one. I checked my project settings and can confirm my issue type, layout, and screens are all associated with the correct things (i.e. not associated with the one I want to get rid of as shown in the screenshot.

Can someone please help me understand what I am doing wrong?

[Trudy Claspill · Accepted solution]

Hello @Jessica Huebner 

That is an indication that your screen is used in another Screen Scheme, which may be associated to another project.

From the first image, go to the Screen Schemes option on the left.

Look for the entry for "SWS: Kanban Default Screen Scheme". The entry will show you if that scheme is associated to any projects.

You would need to modify that Screen Scheme to remove the reference to the screen. However, if that Screen Scheme is used by another project, that could cause a problem in that other project. In that case I would recommend that you make a copy of the "Shift Kanban Default Issue Screen", and then within the "SWS: Kanban Default Screen Scheme" replace that screen with the copy you make.

[Jessica Huebner]

Thank you so much, Trudy! I knew it was something small. You're right - after navigating to Screen Schemes and looking at my SWS: Kanban items, I incorrectly had the Shift issue type screen scheme associated. I was able to remove this (and resolve my issue) by configuring to the correct one.

Thanks again!

[Sayed Fareed]

A screen scheme in the context of issue tracking systems like Jira refers to a configuration that defines which screens are used for different operations within a project. These operations typically include creating, editing, transitioning, or viewing issues.

Here's a breakdown of how a screen scheme works:

1. **Screens:** Screens are user interfaces where users interact with issues. They contain fields that users can fill in with information. For example, when creating an issue, users are presented with a screen where they input details like summary, description, priority, etc.

2. **Screen Scheme:** A screen scheme is a collection of screens that determines which screens are shown for specific issue operations. For instance, a screen scheme may specify that a particular screen is used when creating an issue, a different screen is used when editing an issue, and so on.

3. **Issue Operations:** Issue operations refer to actions that users can perform on issues, such as create, edit, view, or transition (e.g., moving an issue from one status to another). Each operation can be associated with a specific screen or set of screens.

4. **Associating Screens with Operations:** The screen scheme defines which screens are associated with each issue operation. For example, the "Create Issue" operation may be associated with a screen called "Create Issue Screen," while the "Edit Issue" operation may be associated with a screen called "Edit Issue Screen."

5. **Assigning Screen Schemes to Issue Types:** Screen schemes are typically assigned to specific issue types within a project. This means that different types of issues (e.g., bugs, tasks, features) may have different screen schemes associated with them, allowing for customized user interfaces based on the nature of the issue.

6. **Project Configuration:** Screen schemes are part of the project configuration in Jira. Project administrators can define and manage screen schemes to tailor the user experience for their project's needs.

Overall, screen schemes play a crucial role in configuring the user interface and workflow for managing issues within a project in Jira or similar issue tracking systems. They help ensure that users are presented with the appropriate screens and fields based on the actions they perform.