How can I define that two custom made issutypes should behave different than the default Jira issuetypes?

I guess this has to do with Issue Type Schemes, but I do not understand, because I have defiend my own issue type scheme and associated this scheme with my project, but when creating a new instance of my say issuetypeOne I get the fields and behavior I want, but I get the same fields and behavior when creating default Jira issuetypes as well, i.e. bug or new feature.

I guess I am asking if:

1: Should I create one Issue Type Schemes for my two custom made issue types?

2: How do I associate the Issue Type Schemes to make Jira seperate behavior and what is displayed between custum made issuetype and default jira types?

Thank You!



1 answer

1 accepted

0 votes

An issue type scheme tells a project "use this list of issues for this project". That is all it does. Other things are determined by other schemes (field configurations, workflows, field contexts, screens etc)

Try to think of it all separately.

Thanx Nic!



Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,991 views 12 18
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot