Summary

Transition's post-function "Set issue security level based on user's project role" is no longer working when creating a sub-task. The security level for sub-task is always inherited from the parent issue, regardless of the post-function configuration or default security level.

Note

• As per Configuring issue-level security, sub-task will inherit the security level of the parent issue.
• As instructed in the page below, using post-function "Set issue security level based on user's project role" can automatically set the security level for sub-tasks during sub-task creation:
  • How to Automatically Set Issue Security Level for Sub Task During Creation
• This post-function was offered by JMWE add-on previously, however currently it's natively available in JIRA as per JIRA Miscellaneous Workflow Extensions (JMWE) removal from JIRA Cloud

Steps to Reproduce

1. Add two users to JIRA. For example: User A, User B
2. Create a project
3. In the project's People add User A to project role Administrators, and add User B to project role Developers
4. Create a issue security scheme (i.e. Test Security Scheme) with following security levels:
   • Level C (Default)
   • Level D
5. Associate this issue security scheme with the project
6. Edit the project's workflow and add the following post-functions to Create Issue transition using the post-function Set issue security level based on user's project role:
   • If user is a member of the Developers role, set issue security level to Level D (Test Security Scheme).
   • If user is a member of the Administrators role, set issue security level to Level C (Test Security Scheme).
7. Use this workflow for all issues and sub-tasks in the project
8. Log in as User A (Administrators) and create an issue in the project. For example Test Issue
9. Log in as User B (Developers) and create a sub-task for the issue created in the previous step. For example Test Sub-Task

Expected Results

• The security level for Test Issue be set as Level C (as per post-function)
• The security level for Test Sub-Task be set as Level D (as per post-function)

Actual Results

• The security level for both Test Issue and it's sub-tasks (i.e. Test Sub-Task) are set as Level C (which is parent's security level)
• Seems the post-function updates the sub-task'a security level first, and then it will be updated automatically matching parent issue's security level. Following records will be added under History tab in sub-task's Activity:

User B created issue - <time stamp>
User B made changes - <time stamp>