Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-39112

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

    XMLWordPrintable

Details

    Description

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? 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".

      Attachments

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-34148 Permit move operation to retain inactive user as assignee/reporter of the issue

          • Low - Low priority issues
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-43395 Issue Assignee and Reporter is kept when moving an issue, even though user has no permission

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-45421 Assignee not changed when moving issues between projects with different permission schemes

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-44926 JIRA doesnt respect the ASSIGNABLE permission while moving issue

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-45064 On moving Issue to another project, JIRA doesn't check the permission for Assignable User

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-45205 Moving issue between projects will keep the assignee, even if the user is not allowed to assign

          • Low - Low priority issues
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-39112 JIRA is not checking the Assignable User permission when moving an issue between projects

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-68426 Jira is not checking the Create Issue permission for Reporter when moving an issue between projects

          • Medium - Medium priority issues
          • Gathering Impact
          mentioned in

          Page Loading...

          Page Loading...

          was cloned as

          JSEV-421 Loading...

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: