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.

[Alex Koxaras _Relational_ · Accepted solution]

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

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)

[Alex Koxaras _Relational_]

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

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?

[Alex Koxaras _Relational_]

This (look at the upper right corner on the image below) :)

[Hadas Hamerovv]

Wow. I think I followed your instructions but it still does not work. 

I recorded the screen to who everything with the new configuration but your system here does not allow me to upload it.

[Hadas Hamerovv]

And I do not have any validation or custom post functions for this project.

The only validation there is here is:

Only users with Create Issues permission can execute this transition.

[Alex Koxaras _Relational_]

Give me a screenshot of your project's issue type general configuration. Go to project's settings,  issue types. 

[Alex Koxaras _Relational_]

Upload your video to YouTube or somewhere else and paste here the link

[Hadas Hamerovv]

Deleted the link as it is irrelevant

[Alex Koxaras _Relational_]

What I want from you is the following:

For example, on the above screen, my subtasks has the same field configuration as the rest of the issue types. If on this config a field is required then it will be required on the create screen of the subtasks issue type.

[Hadas Hamerovv]

[Hadas Hamerovv]

Hope I understood what you are asking. If not, please be kind to instruct again

[Hadas Hamerovv]

Pwow, I found the reason.

When creating the custom field and giving it a default user value I also set the context to 'All projects'.

That blocked my other project where this specific user is not part of.

So, going back to the custom field and changing the context merely to the project I need it in solved the problem.

@Alex Koxaras _Relational_ I really wish to thank you for the amount of time you've invested here. I truly appreciate the support dedication. I learned a lot about the Jira configuration during this investigation with the material you've provided. Hope this will save me some future mistakes.

Thanks a lot.

[Alex Koxaras _Relational_]

Anytime @Hadas Hamerovv !

I'm glad you figured out the last piece of puzzle! Kindly mark this answer as accepted so as to help other people in this community to find the right answers. Thanx!