Summary

Transition's post-function "Set issue security level based on user's project role" is no longer working when creating an issue. The security level for new issues is always set as default, regardless of the post-function configuration.

Steps to Reproduce

1. Add two users to JIRA. For example: User A, User B

1. Create a project

1. In the project's People add User A to project role Administrators, and add User B to project role Developers

1. Create a issue security scheme (i.e. Test Security Scheme) with following security levels:

• • Level C (Default)

• • Level D

1. Associate this issue security scheme with the project

1. 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).

1. Publish the workflow

1. Log in as User A (Administrators) and create an issue in the project. For example Test Issue A

1. Log in as User B (Developers) and create another issue. For example Test Issue B

Expected Results

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

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

Actual Results

• The security level for both Test Issue A and Test Issue B are set as Level C 

Workaround (updated)

Refer to Resolution 2 or Resolution 3:

• How to set the Security Level of an issue based on group membership

Alternative:

1. Edit the project's workflow and add the post-functions to the Create Issue transition using the post-function Set issue security level based on user's project role
2. Move the set issue security level to based on user's project role field post function to be on top (step 1) of 'Create Issue Post function'