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 change the Field Configuration for one Issue Type in my project?

Katie_xw8pyq

Hello,

For sub-tasks in our projects we do not want to show all of the fields that appear in the other issue types.

I thought I could do this by changing the Field Configuration that the sub-task reference in the Project Settings - Issue Types screen. However, I cannot find any way to change the Field Configuration that a sub-task references.

Thanks in advance for your thoughts!

Accepted answers

John Funk

Hi Katie,

Unless I am missing something, why can't you create a new Field Configuration and then associate the new Sub-task issue type to the new Field Configuration in the Field Configuration Scheme?

All comments

Liam Green

Hi @Katie

We had a similar issue - not sure it is the correct solution, but our workaround was to create a matching request type (Automation can assign it automatically to the issue type) and then change the fields for the request.

You'll find the settings under request types in the project settings.

Hope this helps - let me know if you need anything further

Thanks, Liam

John Funk

Hi Katie,

Unless I am missing something, why can't you create a new Field Configuration and then associate the new Sub-task issue type to the new Field Configuration in the Field Configuration Scheme?

Katie_xw8pyq

Thanks, Liam. We will check this out.

Katie_xw8pyq

Hi John, thanks for answering. We may be missing an obvious step, but we couldn't find where to change the association between issue types and field configurations. I can see where the association is, but not where to change it. Thanks!

John Funk

Do an edit on the field configuration scheme :-)

Grace Tashjian

Hi John,

I modified the custom field configuration scheme so that sub-tasks aren't included in the applicable issue type list. When I created a new sub-task in our project afterwards, it was essentially a blank subtask with none of the fields configured appearing in the task.

Am I taking the right approach here? Am I missing a step?

Thanks!

Grace

Field Configuration Scheme.PNG Empty Subtask.PNG

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud