-
Bug
-
Resolution: Duplicate
-
Low (View bug fix roadmap)
-
None
-
6.0.8
-
6
-
Steps to reproduce
- Create issues in JIRA with a user 'test'
- Set the user 'test' as 'inactive'
- Try to bulk move the recently created issues by 'test' user to another project
- 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.
- Now try to open one issue in the browser and try to move that one issue to another project.
- 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.
- duplicates
-
JRASERVER-9604 Reporter information can be lost when bulk moving issues
-
- Closed
-
Single issue move with inactive user is allowed but not multiple issues move
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
6.0.8
-
6
-
Steps to reproduce
- Create issues in JIRA with a user 'test'
- Set the user 'test' as 'inactive'
- Try to bulk move the recently created issues by 'test' user to another project
- 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.
- Now try to open one issue in the browser and try to move that one issue to another project.
- 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.
- duplicates
-
JRASERVER-9604 Reporter information can be lost when bulk moving issues
-
- Closed
-