Hello @Joshua Hollis
The issue is already in a Closed status.
There are either no transitions available to transition from Closed to another Status, or you don't have permissions to execute those transitions due to a Condition on those transitions.
What are you actually trying to accomplish? Are you really trying to change the status of the issue, or are you trying to accomplish something else?
If you are really trying to change the Status of the issue the workflow will need to be examined to see if 1) there are any transitions configured to change from Closed to another Status, and 2) if there are, whether or not you have permission to execute them.
I've attempted to add a reopen transition to the workflow, and I am prompted to this web page after adding the transition.
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.
Can you show us the unchanged workflow? Are there any transitions from Closed to another status?
If there are not, then to deal with the error that arises when you try to add one you will need to copy the current workflow, make your changes in the copied inactive one and save it.
Then you'll need to add your new workflow to the same/current workflow scheme to replace the active one. But sure to publish it.
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.
Based on the workflow diagram it should be possible to transition the issue from Closed to any other status that has "ALL ->" pointing to it
Being the project lead does not guarantee that you have all permissions. Even being a Jira Admin or a Site Admin does not automatically override restrictions that have been set in a Workflow. That level of admin access does give you the ability to change the restrictions to give yourself the access you need.
The Permission Scheme should be examined to see if there are properties set on the Closed status that prevent it from being changed. The "ALL ->" transitions should also be examined to see if there are Conditions set on them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What do I specifically need to examine in Permission Schemes to enable the movement from Closed Status to a Reopened Status?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1. In the diagram image you provided there is no "Reopened" status, so you can't transitions issues that use that workflow to that status, regardless of your permissions. Is there more than one workflow being used in that project such that you think a status named "Reopened" should be available?
2. To change the status of an issue you need at least the Transition Issue permission. You may also need the Edit Issue permission.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you walk me to where it determines who has super admin levels of access to a project? @Trudy Claspill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As a site admin you should have access to the System settings for Jira.
After selecting that you should be able to select Global Permissions from the panel on the left and find the Administer Jira Global Permission. The groups specified here will have access to administer Jira projects and can therefore modify Permissions for projects to give themselves additional access.
That is what I would call "super admin levels of access".
Users in this group will also need a Jira Software license (managed through admin.atlassian.com) in order to operate the end user functionality in Jira Software projects.
Beyond the above, the admin's permissions in a specific project will be governed by the Permissions applied to the specific project and (in the case of setting the status of an issue) the construction of the workflow (including Conditions, Validators, and Properties specified in the workflow).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online 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.