nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Board Permission

Vielbert Victorio

Hi, I have a question regarding "Delete Issues" Permission, can i actually use account hierarchy, e.g. if i created task for Manager A and B and then Manager A created issue for Head A, Manager A can delete the task he assign to Staff A but Manager B couldn't, if Head A created task for Staff A, i wanted that Manager A can delete Head A assigned task for Staff A but Head A can't delete task that was created by Manager A, is it possible to do so?

Accepted answers

Fazila Ashraf

Hi @Vielbert Victorio

Welcome to community!

In the Permission scheme, you can grant the permission to roles/groups/application access/project lead/a particular usre or issue specific reporter/assignee.

It is not possible to achieve the dynamic permission assignment to an issue by custom rules

All comments

Fazila Ashraf

Hi @Vielbert Victorio

Welcome to community!

In the Permission scheme, you can grant the permission to roles/groups/application access/project lead/a particular usre or issue specific reporter/assignee.

It is not possible to achieve the dynamic permission assignment to an issue by custom rules

Vielbert Victorio

so you mean that, hierarchy permission state is not possible on jira board permission right?

Fazila Ashraf

@Vielbert Victorio , it is not possible.

Also note that 'Delete issue' permission is a project level permission and not a board permission.

Board is only a view to work on a scoped set of issues from project/s.

Vielbert Victorio

i see, thankyou

AKBAR_vb5daf

Hey @Vielbert Victorio ,

You can actually use the 'Issue Security Scheme' and restrict the View access of such created issues using 'Security Levels' and rest of Head and Staff create normal issues and keep them away from the 'Delete Issue' permission. Manager A and Manager B both will be under the 'Delete issues' permission for whole project.

Keep Manager A, Head A, Staff into Level 1 and likewise Manager B and respective Heads, Staff into Level 2.. inform the Staff, Heads to use their respective Levels and thus Manager B can't delete the issues associated with Manager A and vice-versa. Heads and Staff can work on the issues they've created and no point raises of deletion of issues because they can't even view the issues at all which were not associated with their 'Security Level'

Hope this might solve some of your requirements..

Appreciate your Patience..

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud