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?
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.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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!
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