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

Reporter information can be lost when bulk moving issues

      Currently JIRA attempts to validate the issue's reporter when it is being moved. So if the original reporter doesn't have the create issue permission in the target project, then their reporter will be changed.

      While this way maintains the integrity of the destination project (reporters always have the create permission), it's usually not that useful and not particularly intuitive. Generally, people want to keep the reporter data, even if the issue is moved.

      This becomes an especially large problem when users are "deactivated" by having all their permissions removed, so that still have issues they reported even though they don't have the permission to. When doing things that trigger a bulk move like Issue Type Scheme migration, the reporter information for these issues are lost.

      The reporter field should probably be excluded from the move process altogether.

      (NB Not sure if a Bug or Improvment)

            [JRASERVER-9604] Reporter information can be lost when bulk moving issues

            Bugfix Automation Bot made changes -
            Minimum Version New: 3.05
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2841963 ] New: JAC Bug Workflow v3 [ 2926298 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2584445 ] New: JAC Bug Workflow v2 [ 2841963 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1526163 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2584445 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 667585 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1526163 ]
            Wazza made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 73669 ] New: This issue links to "Page (Extranet)" [ 73669 ]
            nd made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 73669 ] New: This issue links to "Page (Extranet)" [ 73669 ]

            Was this fixed in 6.3 or in 6.2.x ?

            JRA-41535 claims that it is not reproducible in 6.2.7.

            Mark Lassau (Inactive) added a comment - Was this fixed in 6.3 or in 6.2.x ? JRA-41535 claims that it is not reproducible in 6.2.7.
            Mark Lassau (Inactive) made changes -
            Link New: This issue is duplicated by JRA-41535 [ JRA-41535 ]

              Unassigned Unassigned
              mark@atlassian.com MarkC
              Affected customers:
              19 This affects my team
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: