In our Change Enablement process, we’ve configured workflow properties on several statuses to restrict editing to our admin group and an automation-specific user.
We want to keep these restrictions but also allow the assignee, or a specific project role, to reschedule the change if needed.
Using the Permission Helper, I don’t see any dependency between the Edit Issue and Schedule Issue permissions, but the properties aren’t behaving as expected. Here’s what we currently have set:
jira.permission.edit.group | groupId
jira.permission.edit.user | accountId
jira.permission.scheduleissue.assignee | (left empty)
I’ve reviewed the documentation on workflow properties and project permissions, but I haven’t found anything indicating that both permissions must be granted together. Has anyone encountered this behavior or found a workaround?
https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/
https://support.atlassian.com/jira-cloud-administration/docs/permissions-for-company-managed-projects/
@Marc - Devoteam @Joseph Chung Yin I found this documentation that solved what I was looking for. Essentially, I added a new status called 'Reschedule change' that allows a transition on any status without granting any additional editing permissions.
These permissions are related, as a transition action is in fact also an edit.
You could grant users edit action and no transition permission, but a user isn't able to transition an issue without granting edit permission as well.
It's the same if you don't grant browser permission, non of the other permissions granted will apply.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the response! I think there may be a misunderstanding, though — I'm not referring to workflow transitions. My issue relates to rescheduling a change by modifying date/time fields (like Planned Start), which is governed by the Schedule Issue permission.
Based on your response, though, I think the same scenario applies, that they can't reschedule without being able to first edit the issue. Is this correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Correct, the scheduling is also an edit action, so the same applies.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is not quite clear of your question, are you trying customize your WF transitions on who can transition the items via workflow. Or, you are trying to locked down editing of items when it is in a specific status?
Kindly advise and provide more information, so we can assist you further.
Best, Joseph Chung Yin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the response! I think there may be a misunderstanding, though — I'm not referring to workflow transitions. My issue relates to rescheduling a change by modifying date/time fields (like Planned Start), which is governed by the Schedule Issue permission.
I've already locked down editing on specific workflow statuses. What I'm wanting is to allow someone to reschedule (edit planned start/planned end) on a change without them being able to edit the rest of the description/specific details in the change request.
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.