-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
3.5.2
-
3.05
-
3
-
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)
- is duplicated by
-
JRASERVER-41535 Single issue move with inactive user is allowed but not multiple issues move
-
- Closed
-
[JRASERVER-9604] Reporter information can be lost when bulk moving issues
Minimum Version | New: 3.05 |
Workflow | Original: JAC Bug Workflow v2 [ 2841963 ] | New: JAC Bug Workflow v3 [ 2926298 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2584445 ] | New: JAC Bug Workflow v2 [ 2841963 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1526163 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2584445 ] |
Labels | New: affects-server |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 667585 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1526163 ] |
Remote Link | Original: This issue links to "Page (Extranet)" [ 73669 ] | New: This issue links to "Page (Extranet)" [ 73669 ] |
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-41535claims that it is not reproducible in 6.2.7.