Bit late to the party, but just why do I need to make our project manager part of the Administrator group on Jira Cloud when all I want is for them to be able to create classic projects.
Not directed at you, Alexey, but rather at Atlassian that recently have been making our JIRA more and more complicated by ever release... continuously using us as guinea pigs for development of the product... No, I don't want "new views" of issues when they obfuscate information and make things much more inaccessible... I have so many frustrated users at the company because productivity goes down when old patterns no longer work and Atlassian forces you to learn something new.. This is not good UX/software design!
Same now with this, I just discovered I had a spate of useless Next-gen projects created by some PMs because the classic option turned out to be grayed out - not to my knowledge since I'm administrator - and the fact I have to make some of them admin is neither to their or my liking.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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