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

Fields changing based on issue type

Logan Query

I've created a new issue type, my question is, how do I associate this with other screens/schemes? I'm trying to have the specific issue only show up with the few fields needed versus the task field where we have a handful of other mandatory custom fields. Is this possible?

For example:
Issue Type: Task
-Assignee
-Reporter
-Priority
-etc..

Issue Type: Risk
-Probability
-Severity
-Mitigation Plan
-etc..

Accepted answers

Valerie Knapp_gp7rpj

Hi @Logan Query , welcome to the Atlassian Community and thanks for your question.

It is possible to have different screen configurations for different work item types. Please see the documentation which explains this here - https://support.atlassian.com/jira-cloud-administration/docs/add-a-custom-field-to-a-screen/ .

Basically, you can have, as in your example, a work item type of task, which has the standard fields and another work item, risk, which has fields which are specific to a risk.

It might be the case this is easier for you to configure in a team-managed project but it depends on what you are trying to achieve.

Let us know if you need more help.

Cheers

All comments

Valerie Knapp_gp7rpj

Hi @Logan Query , welcome to the Atlassian Community and thanks for your question.

Basically, you can have, as in your example, a work item type of task, which has the standard fields and another work item, risk, which has fields which are specific to a risk.

It might be the case this is easier for you to configure in a team-managed project but it depends on what you are trying to achieve.

Let us know if you need more help.

Cheers

Shalini Pradhan

Hello @Logan Query ,

Good day! Welcome to Atlassian Community

For your use case, you can

Create a seperate screen and field configuration for new issue type and add it to the concerned project.

You can find more details here: https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-screens/

Logan Query

I'm trying to change these to be the default setups for the company managed projects. I have configured, at least I believe I have, the risk field configuration properly, but when I try to associate it with the default scheme, I'm unable to do so.

Valerie Knapp_gp7rpj

Hi @Logan Query , thanks for your reply.

I have recorded a short Loom to show you what you would need to do to achieve this configuration.

There are 3 levels of configuration and they are iterative, so, you would need to create a screen for Risks, then a screen scheme for the work item type of Risks, and then add this screen scheme to the Work Type Screen Scheme for the project.

https://www.loom.com/share/688be801bb04441eb3dee5833fd422ce?sid=3ce5f557-febc-4b36-86a4-207e7d7ef49c

In the video, I am showing first, at the project level, that you have different work items which either share a screen configuration (as is the case for the Story, Epic, Task and Sub-task), or have their own custom configuration (like for Bugs).

Once you have a project with the Work Type Screen Scheme configured correctly for the Risks and the rest of the work types, you should be able to 'share settings with an existing project' during the creation of other company-managed projects to make sure they always have the same screen configuration for projects which need to have the Risk work type.

Screenshot 2025-09-19 172140.png

I hope this helps you but if you are still stuck, please let us know and we will try to help.

Cheers

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud