Extended project administration not working - project admin unable to edit non-shared workflow

[Gil Vinokoor]

Hello Atlassian,

On your website (https://confluence.atlassian.com/adminjiraserver085/managing-project-permissions-981154936.html) you state that extended project administration can provide project administrators the ability to edit workflows and screens under certain conditions.

Well, I have a Jira project with a non-shared workflow where the project admin is unable to edit the workflow, despite it being only used by the project in question and it is not a system workflow. (And yes, Extended project administration is ENABLED in the project).

I see that @Derek Mart has asked such a question and Cody Stevens* is familiar with this part of Jira administration, so some clarification and assistance is welcome, as this is frustrating to both the global admins and the project admins at my company.

Note: Using Jira Data Center 8.5.5.

* I am unable to tag Cody since it appears his handle "Cody Stevens (Community)" has HTML format that this Details field can't handle.

[Gil Vinokoor]

Hello, is anyone from Atlassian or the Community able to provide insight or answers to my query above?

[Muhammad Ramzan]

@Gil Vinokoor ,welcome to Atlassian Community. Let me try if i can help you.

Can you please describe your issue, when you taking about workflow edit, what you want to achieve . Project Admins can edit non shared work flows but with some If's.

• The workflow must not be shared with any other projects, or be a system workflow.
• To add a status, the status must already exist in the Jira instance i.e. the project admin can't create new statuses or edit existing statuses.
• To delete a status, the status must not be used by any of the project's issues.
• The project admin can create, update or delete transitions, but they can't select or update a screen used by the transition, or edit or view a transition's properties, conditions, validators or post-functions.

[Gil Vinokoor]

Hi Muhammad,

Thanks for replying. I was aware of all of those limitations and have confirmed that:

1. The workflow is not shared with other projects, nor is it a system workflow.

2. The statuses in the workflow already exist in the Jira instance, i.e. no statuses added.

3. Not relevant - I am not trying to delete any statuses.

4. Not relevant - the project admin is not even able to click "Edit" on the workflow, let along edit transitions.

So...any other ideas? Anyone else?