Subtask security level is stuck in cases where it is not synced up with the parent issue

XMLWordPrintable

    • 1
    • Severity 2 - Major

      Issue Summary

      Subtasks inherit their issue security level from the parent. The security level cannot be modified on the subtask itself. Two scenarios have been observed where the subtask is out of sync with the parent issue:

      1. The subtask is created under a parent that has an issue security level applied and thus inherits this level. The parent is then changed to another parent without a security level, the security level is not cleared on the subtask
      2. In rare cases it was observed that when using automations to create subtasks and setting the security level of the parent using a different automation rule, the first subtask created may not inherit the level and causes the sync issue

      Steps to Reproduce

      Since the 2nd issue is harder to reproduce as it appears to be a race condition of sorts, the following reproduction steps can be used to demonstrate the behavior.

      1. Create an Issue Security Scheme within Jira
      2. Add a security level such as Test to that scheme
      3. Associate the scheme with a Jira project such as EXAMPLE
      4. Ensure that the Security Level is added to the issue edit / view screens
      5. Create a Jira issue (EXAMPLE-1)
      6. Create a subtask for that issue (EXAMPLE-2)
      7. Set the security level on EXAMPLE-1 to Test and confirm that EXAMPLE-2 has inherited the level
      8. Create another Jira issue (EXAMPLE-3)
      9. Open up EXAMPLE-2 and update the subtask's parent issue to EXAMPLE-3

      Expected Results

      Since EXAMPLE-3 does not have a security level applied, subtask's security level should be synced from the new parent and cleared out.

      Actual Results

      The subtask EXAMPLE-2 is now stuck with the security level that cannot be modified on the subtask itself.

      In the case of the automation rule, the subtask will be missing the security level even though the parent has the security level added.

      Workaround

      In case the subtask still has a security level while the new parent does not, adding a level and then removing it should re-sync it.

      On the flip side, if the parent has a security level but the subtask did not inherit it, remove the security level of the parent and add it back, which should also re-sync the security levels.

            Assignee:
            Dong
            Reporter:
            Andras M.
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: