Hi I currently have a project that is in a global permission scheme that has "Delete Own Attachments" locked down to just jira-administrators. I have seen properties you can add to the workflow that put this permission down to the workflow status level using jira.permission.attachdeleteown.group. I tried that and using a different group than jira-administrators and it didn't seem to work. Is there a way that a workflow property can "overrule" the permission scheme for that project?
Thanks!
It can be MORE restrictive, but not less
Gotcha! So my only option if I wanted to change this JUST for this project but not all of them in that permission scheme would be to make a new permission scheme just for this project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Cameron Palmer ,
Like Joe already said, those properties can only restrict but not grant permissions.
If you still want to use the same permission scheme globally, project roles are your answer (see https://confluence.atlassian.com/adminjiraserver/managing-project-roles-938847166.html). You can add a project role to your 'Delete Own Attachments' permission and only put users into this role - either via group or single users - within your special project.
Cheers
Thorsten
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
At the American Academy of Family Physicians, siloed marketing teams faced delays and duplicate work. Kerrie Gottschalk shook things up by moving the department to Jira, streamlining processes, boosting visibility, and sparking stronger collaboration.
Read the story
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.