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 to separate an issue types scheme and field scheme which are shared between projects?

Stahl, Yoav

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

Accepted answers

Mikael Sandberg

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.

All comments

Mikael Sandberg

Hi @Stahl, Yoav,

Welcome to Atlassian Community!

Stahl, Yoav

Hi
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

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

Stahl, Yoav

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?

AGAIN THANK YOU THIS IS REALLY MUCH APPRECIATED!

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