Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to separate an issue types scheme and field scheme which are shared between projects?

Hi all
As explained in Associating issue types with projects one can "A single issue type scheme can be "re-used" across multiple projects so that a group of similar projects (i.e. projects which might be used for similar purposes) can share the same issue type settings."

Similarly one can share field scheme between projects.

I have a project which has issue type scheme  as well as field scheme which is shared between many projects.

I am now faced with

1. a new need to add new issue types ONLY FOR MY PROJECT. I do not want to add the types to any other project.

2. a new need to add new fields ONLY FOR MY PROJECT. I do not want to add the fields to any other project.

I wish to have the same issue types and fields as I had before and only add new issue types and fields on top of them.

Is there a way to do this without creating a new issue type scheme and new fields scheme from scratch?
Thank you

1 answer

1 accepted

1 vote
Answer accepted
Mikael Sandberg Community Leader Nov 29, 2022

Hi @Stahl_ Yoav,

Welcome to Atlassian Community!

You will need to create a new issue type scheme in order to do this. But for the new custom field you can change the configuration so that the field is only associated with this new issue type or with the project, that way you do not have to create a new field configuration scheme. 

Thank you!
So for issue type scheme I will have to create it from scratch correct?

Regarding custom fields - do you mean I can create new fields just for my project without changing the field configuration scheme? How will I associate these new fields into my existing issue types (for example epics, stories etc) without changing field configuration scheme? if I have to change the scheme I am back to square one as I cannot change the current scheme as it is shared by many projects :(

Thank you again

Mikael Sandberg Community Leader Nov 29, 2022

No, you can copy the existing issue type scheme and then just add the new issue type to it and assign the scheme to the project.

Yes, if you go to Settings > Issues > Custom fields and click on the three-dot menu on the right of the field you will see Contexts and default value. From here you can change the configuration so that the field is only associated to a specific issue type and/or a specific project.

Screenshot 2022-11-29 at 7.45.19 AM.png

Like Stahl_ Yoav likes this

Again thank you very much!!
Regarding the first point - sorry to ask such a stupid question but I might have missed it or do not have permissions but I cannot find how do I copy an existing issue type scheme :( can u please advise?

Regarding the second point - if I understand correctly this DOES change the (shared) field configuration scheme but this change is only visible for the selected projects (aka applicable context)
Is that correct?


Mikael Sandberg Community Leader Nov 29, 2022

To make a copy of the issue type scheme just go to Settings > Issues > Issue type schemes and under actions you have the option to copy a scheme. And note that you need Jira admin permission to do this.

Changing the configuration of the custom field will not change the shared field configuration scheme. You would still see the custom field in the scheme, but the field would only be visible to the issue types/projects that you have defined in the context. The only time you would have to create a separate field configuration scheme would be if the custom field should be required in one project but not in any other.

Again thank you.

Unfortunately that is exactly the case for me :( I need a few custom fields which are only available in my project and not in any other project.

That means I will need to clone the field configuration scheme? is that possible similarly to the above?

thank you

Mikael Sandberg Community Leader Nov 29, 2022

Yes, just create a copy of the existing scheme and then update the project to use the new one.

Like Stahl_ Yoav likes this

Suggest an answer

Log in or Sign up to answer