-
Suggestion
-
Resolution: Unresolved
-
None
-
257
-
35
-
Issue Summary
This is reproducible on Data Center: No
New permission 'Edit Workflow' which has been introduced as part of JRACLOUD-70190 doesn't work with Jira Service Management company-managed project.
Same with Manage Issue Layouts permisson as well.
Updated - Documentation currently mentions these limitations related to JSM project: https://support.atlassian.com/jira-cloud-administration/docs/permissions-for-company-managed-projects/#Administration-Permissions
Steps to Reproduce
- Create a new JSM project (OR use existing one). It must be company-managed project
- Make sure Workflow used within the project is NOT shared with another project
- Assign project admin role to the user - (This needed otherwise user will only be able to view the Workflows tab
- Assign 'Edit Workflow' and 'Browse Project' permission to the user
- (Optional) Use Permission Helper to verify user has correct permission
- Now log in as the user and navigate to Project Settings > Workflow
Expected Results
User should see Edit workflow hyperlink
Actual Results
There is no link for Edit workflow
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
- Closed
[JRACLOUD-85127] Edit Workflow and Manage Issue Layouts permission doesn't work with JSM company managed projects
Hi all this is a known limitation, as extended project administrator is not yet supported in JSM. Please vote and comment with your use-cases so our team can consider JSM support as part of our future prioritisation for this feature.
Kind regards,
Aditi Dalal
PM, Jira Permissions
All comments
We need this as it's very unlogical to disinguish between "normal" and JSM projects. Users at least do not understand it.
Hi,
Same problem here, extreme extra work for us Org. admins because of these small adjustments in the workflows that a JSM admin could master in the same way. Unfortunately, this adds up and this feature would be very important.
Cheers
Hey guys,
Our team is really disappointed to see another great feature that was loudly announced with multiple purple, and yellow popups on the JSM project screens to be limited again to Jira Only.
It's a must-have feature for all big enterprise companies using JSM.
We are hoping this functionality will be released as soon as possible.
Hello, this feature would be really helpful to our team as we are constantly updating workflows. In general, people update workflows need to be able to do it without first reaching out to whoever is managing the JSM
This isn't a bug, etc.
This spotlights a malfunctioning/dysfunctional product offering and is a complete oversight by Atlassian Devs/Management.
Launching a product without properly assessing "basic permissions needs" seems like a lack of prioritizing efficiency and/or security....
Hopefully this is remediated quickly. 
Hi,
This feature for JSM would be great because the Atlassian admins would be relieved by 70% and the project admins would have fewer dependencies on the Atlassian admins.
Cheers
Adding my vote. Really need a way for competent Project Admins to self serve changes without giving Jira admin.
It is a great opportunity for Jira Software and why should it not be part in JSM too?
Agreed to the comments below.
This missing functionality has and will continue to slow down my team's ability to self serve changes we could previously make in the self hosted version of Jira. We now have to stop what we're doing, context switch to filing a request to our IT team, wait until they process the request and take action (spending their time unnecessarily), and then once the request is processed, we can pick back up on the flow we were working on.
Not only is this inconvenient and creates additional work for two teams, it is something we could previously self serve in locally hosted Jira and is something we were shown was available in the migration resources.
I really hope this fix is appropriately prioritized as functionality that customers already expect to exist.
This would be incredibly helpful in our instance, where allowing project admins to edit their own workflows makes logical sense.