Why JIRA changed new projects creating behavior?

Previously, when I created a new Agile Scrum project, it is assigned a Default Issue Type Screen Scheme.
Now a new project is assigned KEY: Scrum Issue Type Screen Scheme in which there is no Issues as the New Feature, Task, Improvement.
Also, for each project creates new Screens and Workflows.
Why JIRA changed new projects creating behavior?
I broke my JIRA? Or this is normal behavior?

1 answer

Hi Damir,

I believe this changed so that Project Admins would not make changes to the default schemes, however there is a feature request to address this at https://jira.atlassian.com/browse/JRA-39966

I would suggest adding yourself as a watcher to that so you're notified of any updates, as well as providing feedback directly on that ticket for the dev team.



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 ...

3,338 views 14 20
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