We have a use case where we need to allow our customers to be assignable users for early parts of the workflow.
To do this we're using workflow with an assign button and step properties that deny their access later in the workflow while we work on their issue.
We also give them access to edit issues using the same mechanism.
When the issue is created the properties are:
jira.permission.assign.denied.group.1 = Developers
jira.permission.assign.denied.group.2 = Customer
but we find this also adds the "Admin" button to add a custom field.
so we added
jira.permission.admin.denied.group.2 = Customer
but this removes the "edit" option in the workflow and we can not work out why.
Does anyone have any idea why when we deny a group the admin button appears, and when we deny admin both the admin AND the edit button are removed?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs