Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-39112

JIRA is not checking the Assignable User permission when moving an issue between projects

XMLWordPrintable

      NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.

      Summary

      On moving Issue to another project, JIRA doesn't check the permission for Assignable User. JIRA should not fill that Assignee field during moving an issue, if the former assignee doesn't have Assignable User in project B.

      Steps to Reproduce

      1. Create an issue in projectA
      2. Give UserA Assignable User permission for projectA
      3. Assign the created issue in projectA to UserA
      4. Create projectB
      5. Move Issue from projectA to projectB

      Expected Results

      Assignee field should be left blank as they original assignee doesn't have permission in projectB.

      Actual Results

      The original assignee is still assigned the issue in projectB although he doesn't have Assignable User permission in projectB

      Notes

      The Reporter field is also affected by this bug in the same way as described for the assignee field.

      Issues can be also moved to another project  through "bulk change".

      Workaround

      Configure automation as below in the destination project.

        1. Screenshot 2023-09-28 at 2.02.25 pm.png
          Screenshot 2023-09-28 at 2.02.25 pm.png
          63 kB
        2. onIssueMove.groovy
          1 kB

              apawelczyk Artur Pawelczyk (Inactive)
              jworley Jason Worley (Inactive)
              Votes:
              32 Vote for this issue
              Watchers:
              51 Start watching this issue

                Created:
                Updated:
                Resolved: