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

0 votes

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 Sign up to answer
Community showcase
Posted Oct 16, 2018 in Jira

Looking for anyone who made the switch to Data Center

The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...

77 views 0 3
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