I have added 2 people to the 'developer-E2S' group (self-created group), but now it seems that the user created by someone else before my time (oldest user) can change statuses in issue tickets, and the newly created user can't change statuses of tickets...
My colleague can also change statuses (JIRA admin), while I can't change statuses (also JIRA admin). We have searched for many hours already on how to set it to be able to change statuses, but my colleague can't even recall how he did it for himself (as it's way too complicated to find anything in the cluttered mess JIRA calls "configure system")
solution:
Hello everyone,
We managed to find out where the issue was. Apparently it was as simple as the fact that my colleague forgot to click on "start progress". Once he did that the users were able to change issue statuses.
Thanks for all the support you guys provided!
Thanks so far everyone for the support, I have logged a ticket @ support.atlassian.com. Unfortunately none of the answers here were able to help me as it's not a group, permission or workflow issue (checked all of them and they're all set correctly).
Good luck with your ticket. Please post the outcome later.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Willian,
If it helps, we can take a further look into your configurations. Just raise a ticket on Atlassian SAC (support.atlassian.com) under Atlassian OnDemand.
Though, solutions that other users mentioned might be valid.
Please be aware that admins (via Global Permissions) will have permission to perform most JIRA administration functions. To be able to manage projects and control what happens on it, you will need to set up the proper Project Permissions. One thing that might help you out is the use of the 'Permission Helper' feature. Have you tried it already?
Kind Regards,
Elisa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Elisa, Included in link is a screenshot of the permission helper. It says the exact same for both users. https://www.dropbox.com/s/ekp7ns95fs515og/2014-12-02%2007_58_43-Permission%20Helper%20-%20daikin.onjira.com%20JIRA.png?dl=0 It says that he has the rights to transition statuses (same for me), but neither of us can change the status...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Notice that there's a difference between Global and Project permissions. To which permissions this group is associated with? A possible solution maybe that your user doesn't have the relevant permission for tickets in a specific project.
Screenshots might help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter, The fact that there's only 2 people in that specific group, of which 1 can change the status but the other one can't would suggest that it can't be a group issue. As for screenshots I wouldn't even know where to begin, JIRA has like 20 different locations with permissions to be set, each with 20 options of their own making it very confusing for someone that doesn't breathe JIRA to find his way back in that maze of settings.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Have you checked workflow conditions? May be any defined condition is preventing workflow transition.
Tuncay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John,
I rechecked numerous times, both on myself & my other admin colleague (we're both in all the same groups), as with the 2 other people (both in same developer groups), the 'old' people can change statuses (back from in the days someone else set up JIRA OnDemand), the newbies (myself & the 2nd developer) can't change statuses.
I'd have thought that admins would have full rights by just joining the group, but fact that I can't change statuses proved me totally wrong...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Look at the corresponding permission scheme, see if the transition issue permission is set. If that is ok, look at the workflow and check if there is a condition that prevents you transitioning the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
did you made sure they are in the right group? compared the groups of the users in the developer-E2S and the older groups. Also make sure the person is added to the project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.