Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Share issue type between Projects

I have an issue type where its shared between 2 other projects

Now I want to create a new screen scheme for one the project workaround I have done

1- copied the current scheme

2- renamed the schame and added the new screen I wanted.

3- associated the new scheme to the issue type in issue type screen scheme.

I see the issue type has a different screen scheme

But the Problem is 

it still shows that the new scheme is shared with 2 more projects.

anyone know how can I manage to other projects should use the same "Old" screen scheme and 1 project should use the new screen scheme.

I appreciate your Help in advance. 


1 answer

Hi @Muhammad,

If you associated your new screen scheme to an existing issue type screen scheme, then you have just added your freshly created screen scheme to all the projects the issue type screen scheme was already associated with. And probably that is 2 projects.

If you click on the link that says the screen scheme is associated with 2 projects, you will see which projects they are.

Just to make things a bit clear.

Project >> Issue type screen scheme >> Screen schemes >> Screens 

In a project you use screens to associate issue types with the appropriate custom fields for each issue type.

Every issue can be created / edited / viewed. So essentially for 1 issue, you can define 3 different screens, one for each operation.

You define a screen scheme to package those 3 screens nicely together.

But your project has also multiple issue types, potentially. To link issue types to the appropriate screen schemes, you use an issue type screen scheme. In that scheme, you define which screen scheme is associated with each issue type in your project.

If I understand your explanation correctly, you should create an additional issue type screen scheme to separate the configuration of your different projects.

Hope this helps!

Mikael Sandberg Community Leader May 20, 2021

A good overview on how the screens, schemes, and fields are related can be found here, Project screens, schemes and fields (yes, the document is for Server/Data Center, but it works the same on Cloud).

@Walter Buggenhout _ACA IT_ 

Thanks for replying I have created a new screen scheme and associated with desired project too.

But the new scheme show shared with other projects that using same issue type

Yes, I understand. Usually that is what you would want, as it makes sure that a same issue type is using the same screens (and custom fields) across your entire Jira instance. That helps to create a common understanding across your organisation of  a story, a bug or a task.

But if that is not what you want, identify those projects and associate them with a different issue type scheme.

If you have project A and project B, they both have Story / Bug / Task / Epic as issue types. And let's assume Story and Task and Bug shared the same screens, Epic has its own screens and now you would like to create separate screens for Bug in Project A, but not in project B, you would need to create the following setup:

> Issue Type Screen Scheme for Project A (NEW)

  >> Screen scheme for stories and tasks

  >> >> associated with Story, Task

  >> Screen scheme for Epics

  >> >> associated with Epics

  >> Screen scheme for Bugs

  >> >> associated with Bugs

> Issue Type Screen Scheme for project B (OLD)

>> Screen scheme for stories and tasks

>> >> associated with Story, Task

>> Screen scheme for Epics

>> >> associated with Epics

And so you associate the correct issue type schemes with the correct projects. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

314 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you