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

Can't figure out the configuration/configuration scheme relationships

Hadas Hamerovv

I have two projects. For each I have created a different configuration scheme.

When I look at the issue types, they are all associated to one field configuration.

And I can't figure out where to Associate all issue types in project B to field configuration B and make that in configuration scheme B.

I believe that the fact I cannot create a sub-task is due to that reason since in project A I have a custom assignee field with default user which is not part of the project B team.

Accepted answers

Alex Koxaras -Relational-

Hi @Hadas Hamerovv ,

Go to project B
Go to project settings
Go to fields
On the upper right corner click actions > use a different scheme
Click your desirable field config scheme

field config.png

Let me know if this is what you wanted to do.

All comments

Alex Koxaras -Relational-

Hi @Hadas Hamerovv ,

Go to project B
Go to project settings
Go to fields
On the upper right corner click actions > use a different scheme
Click your desirable field config scheme

field config.png

Let me know if this is what you wanted to do.

Hadas Hamerovv

I thought so. I did it and indeed the subtask is associated with this new scheme.

However still I cannot create a new subtask for some reason. Maybe the 'create screen' is still the one which is common to this project and project A?

Or...I actually don't know what the reason is but I receive this error message:

Code reviewer (A custom field I added to the other project) is set to a user which is not in this project (B)

Screen Shot 2021-09-19 at 14.10.16.png

Alex Koxaras -Relational-

Here's a little diagram to help you understand better the relationship among the different configurations in Jira:

fields_diagram (1).png

If you are interested in learning more, please read this: https://confluence.atlassian.com/adminjiraserver/project-screens-schemes-and-fields-938847220.html

Now, to our problem: Sub-tasks can be created only if a parent exists. So you have to make a parent-child connection during the creation screen.

The way I see it is that subtasks are using the same create screen which are used in another issue type. And possibly I would check that this field configuration which I have associated with the subtasks, doesn't contain any required field, except those needed.

GO to cog >issues >screens
Either create three new screens, or copy from existing ones
Rename these screens as e.g.
- NAMEOFPROJECTKEY: Subtask Create Screen
- NAMEOFPROJECTKEY: Subtask Edit Screen
- NAMEOFPROJECTKEY: Subtask View Screen
Now click on Screen Schemes and create a new one
- Choose for the Create operation the create screen
- Choose for the Edit operation the edit screen
- Leave the view screen for the default
Click issue type screen scheme
FInd your project's issue type screen scheme and click edit
Click Associate an issue type with a screen scheme
Choose subtask and the new screen scheme you have created
Click Add

The above procedure will yield separate screens for the subtask issue type.

Finally I would check the workflow that the subtask is using. You might have a post function or a validator which contradicts with the issue type. If you do, let me know and we'll go through the workflow operation.

Hadas Hamerovv

Alex,

What is cog?

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

configuration

field-configuration

scheme