How can I change the Security Level on a sub-task to be different from the parent? Now the edit screen says "The security level of subtasks is inherited from parents."
You can try and prepare workaround to achieve this:
1. Create custom field Group_Name_x (Group Picker type) and add it to screens
2. Add all groups with people whose are candidates to have access to browse permission (or to role and then this role to browse permission)
3. Add Custom field Group_Name_x to security level. Be carefull and don't include people from groups for subtasks to this security level.
4. Now you can add different values in Custom field Group_Name_x (when create/edit task or subtask)
You can do it without using script is you add a Post Function 'If user is a member of the Internal Access role, set issue security level to Internal' at the Create Issue stage. I have also added a validator that states 'Only users with Edit Issues permission can execute this transition. ' as our clients do not have edit rights. This way all our sub-tasks stay internal.
Hi Nic, we have a security level called Internal and the only group with access to it is a group with internal users so it does work. Every sub-task created of a client specific log is automatically set with 'Internal' security level and it is only visible to internal users.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
EaglePicher Technologies is a leading manufacturer of battery systems for diverse industries like defense, aviation, space or medical. As they operate in highly regulated industries, keeping a clear ...
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