Can I add a section or tab to a Jira software issue view?

[Phil Bustin]

Can I add a section or tab to a Jira software issue view?  So far, I haven't found an answer, except in JSM (can't use that).  I thought I actually did this many months ago, but I can't find that work.

[Trudy Claspill]

Hello @Phil Bustin 

For a Company Managed project you can add a Tab to a Screen.

The option is not available yet for Team Managed projects.

https://jira.atlassian.com/browse/JSWCLOUD-18422

[Phil Bustin]

Thank you.  Near as I can tell, that's only for a transition screen; that is to say, there's no way to assign a screen to a status.

If there is no way to add a tab or section to a default status screen, is there a way to add a dozen or so fields to the More tab?

[Trudy Claspill]

The screens I pointed out above can be used for the Create/Edit/View Screens for issues (when compiled into Screen Schemes) or can be used associated with status transitions in workflows.

I'm not sure what you mean by the "default status screen". Can you provide a screen image?

[Phil Bustin]

I'm only going by experience.  When editing a workflow, I can assign a screen to a transition, but not a status.  I have no experience compiling a screen into a screen scheme.  Also, in the Sandbox, I've inherited existing schemes and configurations, and I'm leery of changing anything that might affect other entities.

At any rate, if I can create a screen with sections or tabs, without affecting global settings, I will.  I just don't know quite how or where.

[Trudy Claspill]

In Company managed projects you can assign a screen to a workflow transition. When the transition is selected, the screen is displayed. There is no feature for associating a screen to an issue status value.

In addition to Transition Screens you create screens that will be associated with the Create Issue dialog, and with the Viewing and Editing of the issues. Those are the screens you group into Screen Schemes. Screen Schemes get grouped into Issue Type Screen Schemes.

The grouping hierarchy is 

Issue Type Screen Scheme
|-- Screen Scheme
    |-- Screens

First you build the screen with all the fields you want to use when you are either Creating, Viewing, or Editing an issue.

In a Screen Scheme you associate the Screen you created to the operation (Create, Edit, or View).

In an Issue Type Screen Scheme, you associate the Screen Schemes to Issue Types. You might have one set of fields that you use for Epics, another set for Stories, a third set for Bugs, and a fourth set for Subtasks.

You can reference this documentation and the child and related pages to learn more about managing Screens, Screen Schemes, and Issue Type Screen Schemes. This all applies only to Company Managed projects. None of this applies to Team Managed projects.

https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-screens/

The screen image I supplied above pointing to the Add Tab option is in the Screen Configuration functionality. That is where you create/configure the screens that are used for Workflow Transitions or Issue Operations.

[Phil Bustin]

Thank you.  This is a bit of a side track, but please confirm the following, just to help me understand: I have a screen I assigned to a transition.  I see that its Default is Used for all unmapped operations.  Should this be different?

When I created it, I also created a Screen Scheme for it.  It is working.  When in the dialog box shown in the screenshot below, if I click Associate an issue operation with a screen, I can select from a large list of screens, but not the one I'm viewing in the Configure Screen Scheme dialog box.  I assume that is as designed, and that there is no reason in fact to try to associate an issue operation with the transition screen I'm viewing.

[Trudy Claspill]

Hello Phil,

In the Screen Scheme when you see Default in the Issue Operation column that means that screen will be used for issue operation (Create, Edit, View) that are not explicitly mapped to a difference screen.

In this example the screen Create Issue Screen will be used when an issue is being Created, and the screen ATP: Scrum Default Issue Screen will be used when the issue is being Viewed or Edited. This is a common configuration if there are fields you want to have people set when they are creating issues, and then you don't want them to be able to edit the fields later. You make the fields available on the screen that is associated with the Create operation, and you take the fields off the screen associated with the Edit and View operations.

It is perfectly fine to have one screen used for all operations. Not "all operations" means Create, Edit, and View. Operations does not include workflow transitions. If you click the button to associate a screen to an operation it will indeed not show the screen that has already been mapped to Default, because that screen is already going to be used for all Issue Operations that aren't mapped explicitly to a different screen.

Typically screens associated with workflow transitions are different than the screens used for issue operations. During a workflow transition usually only a few fields might need to be filled in, so a custom screen is created with just those fields. For example on transitions to a Done status you may want the user to log work and set the Resolution, so you  create a screen with just the Resolution field and the Time Tracking fields, and associated that screen to the workflow transition.

Screens that need to be used in Workflow Transitions do not need to be included in Screen Schemes unless you want that same screen used for an issue operation (Create, Edit, or View).

[Phil Bustin]

So, should I somehow remove my transition screen, that is only to be used for that transition (or multiple transitions), from its screen scheme?

[Trudy Claspill]

If you don't need to use that screen for the Create, Edit, or View operations on issues, and if you have not included that Screen Scheme into an Issue Type Screen Scheme, then you can simply delete the Screen Scheme.

[Phil Bustin]

I keep trying to create an issue type screen scheme and issue type screen with the screen set for View, but I don't see my screen when I view an issue.  Also, I wanted to keep the default fields as they were and add tabs, but when I create a screen, all those fields I see in the existing story I'm using with my workflow are gone.

Is there a way of creating a screen that looks like my existing screen, that I inherited with this project, to which I can add tabs?

[Trudy Claspill]

There used to be a separate pop-up dialog for Edit like there is one for Create. That was eliminated. Now when you view the issue details you are able to edit fields at the same time. If you have fields that you want to be editable, they need to be on both the View and Edit screens. 

To create a new screen that is a modifications of the current screen:

Look at your Project Settings. Click on Issues > Screens.

That shows you the Issue Type Screen Scheme.

It will show you each Screen Scheme and the issue types to which it is associated.

Which issue has the screen that you want to copy and modify? Expand the screen scheme associated with that issue type. That will show you the Screens associated with the Issue Operations. Make note of the screen name.

Go to the gear icon and select Issues. Then select Screens. Find the screen you noted previously. In the Actions column click the ... button and select Copy. That will make a new copy of that screen. You can modify the copy of the screen to add Tabs.

To incorporate that Screen into your project you will have to include in a Screen Scheme and an Issue Type Screen Scheme that is or can be associated with your project. If the Screen Schemes and Issue Type Screen Scheme currently associated to the project are not associated to other projects, then you can modify those without affecting other projects. If they are used by other projects, you will need to make new (or copy) the schemes to build up schemes that you can associate to this project without changing the schemes used by the other projects.

Under gear > Issues > Screens you can see each screen and the Screen Schemes that use it.

Under gear > Issues > Screen Schemes you can see each Screen Scheme and the Issue Type Screen Schemes that use it.

Under gear > Issues > Issue Type Screen Schemes you can see each Issue Types Screen Scheme and the projects that use it.

You will need to note for your project all of the three items listed above that it currently uses, and then look those items up in the above areas to figure out if the items are shared with other projects.

[Phil Bustin]

I will review this.  In the meantime, a consultant has provided the screen I wanted, and showed me how it was done.

[OriO]

And could you share the how the consultat did it, here?

I'm block with the same issue. I have Jira admin access and I cannot make the tab appers in the tab that I have created :(