IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-41535

Single issue move with inactive user is allowed but not multiple issues move

      Steps to reproduce

      1. Create issues in JIRA with a user 'test'
      2. Set the user 'test' as 'inactive'
      3. Try to bulk move the recently created issues by 'test' user to another project
      4. Notice that JIRA forces to change the reporter from 'test' to another active user. This is expected behaviour as per : https://jira.atlassian.com/browse/JRA-34148.
      5. Now try to open one issue in the browser and try to move that one issue to another project.
      6. Notice that JIRA does not complain about the reporter now and allows to move the issue.

      NOTE : This issue is not reproducible in 6.2.7 version of JIRA. So most likely its a bug in the older releases.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-41535

            Single issue move with inactive user is allowed but not multiple issues move

                Steps to reproduce

                1. Create issues in JIRA with a user 'test'
                2. Set the user 'test' as 'inactive'
                3. Try to bulk move the recently created issues by 'test' user to another project
                4. Notice that JIRA forces to change the reporter from 'test' to another active user. This is expected behaviour as per : https://jira.atlassian.com/browse/JRA-34148.
                5. Now try to open one issue in the browser and try to move that one issue to another project.
                6. Notice that JIRA does not complain about the reporter now and allows to move the issue.

                NOTE : This issue is not reproducible in 6.2.7 version of JIRA. So most likely its a bug in the older releases.

                        Unassigned Unassigned
                        rtandon@atlassian.com Ruchi Tandon
                        Votes:
                        2 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            rtandon@atlassian.com Ruchi Tandon
                            Affected customers:
                            2 This affects my team
                            Watchers:
                            3 Start watching this issue

                              Created:
                              Updated:
                              Resolved: