question about Issue Type Screens

[Jeff Laurenza]

I'm not too knowledgeable when it comes to the Issue Type Screens for a Jira project or if I really even need them.
I have a project created for Change tracking. What I was expecting to see was that a user would open a Jira ticket, fill out the information.
The Workflow has the ticket waiting for approval after creation.

The manager(s) open the ticket and review the change request and if approved they assign the ticket to an engineer, or they can reject the the change. But when they click to change the status field, an edit screen pops up and they have to make the change there, instead of just changing the status in the ticket.

This also happen for users who are working the tickets, anytime they change the status field they get a popup window where they have to make the actual change.

I would rather just have the users that interact with a Jira ticket just make the change in the actual ticket and not have make the changes in the popup windows. 

Is this due to having Issue Screen Types?

can I just delete the Screen Types from the project?

Thanks for any help!

[Trudy Claspill · Accepted solution]

Hello @Jeff Laurenza 

Welcome to the community.

Is your project a Software project, Service project, or Business project? It will say at the below the project name at the top of the navigation pane on the left.

Is it a Company Managed project or a Team Managed project? That will be at the bottom of the navigation pane on the left.

Issue Type Screens will apply only to Company Managed projects.

Generally screens that pop open when changing the Status of an issue are screens that have been added to the Workflow for the issue type.  These screens will have been created in the administration Settings > Issues > Screens page by a Jira Administrator. These screens are generally not included in a Screen Scheme or an Issue Type Screen Scheme.

You generally should not delete screens from the Screens page unless you know exactly where they are being used.

If you don't want a pop-up screen displaying when the Status of an issue is changed, you would need to modify the Workflow for that issue type and remove the association of the screen from the transitions where screens are popping up. However, you should assess why that screen is popping up. Does that screen require the user to enter additional data when they change the issue Status? If the screen doesn't display, how would you enforce entering that additional data?

Note that for a Company Managed project, only a Jira Administrator will be able to modify the workflow. They will also need to assess if that workflow is used for other issue types, or is in a Workflow Scheme that is associated with other projects. If the workflow is changed it could affect more than just your project.

With regard to the project configuration, if you are using a Company Managed project then your screens and schemes will have been set up by a Jira Administrator, and it will take a Jira Administrator to change that. The structure of screen configurations is:

Screens - the layout of fields on a screen. These can be used when you create, view, and edit issues or when you change the issue Status

Screen Scheme - A container that associates a given screen with an issue operation (create, view, edit)

Issue Type Screen Scheme - A container that associates Screen Schemes to types of issues. The Issue Type Screen Scheme gets assigned to Projects.

You must have an Issue Type Screen Scheme associated to your Company Managed project. It must include at least one Screen Scheme which could be set as the Default (associated to all issue types in the project where the Issue Type Screen Scheme is assigned). Your Screen Scheme must include at least one Screen which could be set as the Default (associated with all issue operations - create/view/edit - for the issue). Defaults for all of these are created when a Company Managed project is created, if that project was not specified to Share the configuration settings of another project.

In addition to the above you can have screens that are used only in the Workflow during Transitions (Status changes). Those screens may or may not also be used for issue operations in a Screen Scheme.

If you are using a Team Managed project, then the guidance above is not applicable.

[Danno]

@Jeff Laurenzatake a look at this page for more information. I recommend you print out the visual from that page to hang up as a reference.https://confluence.atlassian.com/adminjiraserver073/project-screens-schemes-and-fields-861253368.html