still no answer to this ... i am having the same issue :-(
We had to ask support to help find who the actual admin was.
Turned out it had a different email associated than who we thought. Once we logged in with that email address, we were able to give rights to be able to do this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am the JIRA Admin (also org and site admin for my instance). When I click to create objects it does the next gen projects by default and I want to create a classic project. This blocks us.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i have the same problem, this happened after requesting to have sub-tasks enabled for next-gen projects. this didn't work, now I cannot even create a normal project!! very frustrating
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same thing -- I have admin rights, but Classic is grayed-out.
My colleague with the same privs is not experiencing the issue five feet away.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Make sure that you are a Jira administrator.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.