Details
-
Bug
-
Resolution: Invalid
-
Low
-
None
-
None
-
None
Description
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Issue Summary
When a user imports an issue into JIRA 7.1.X, he or she is named as the issue creator while the reporter of the issue originally is marked as the reporter.
The above causes a lot of confusion when the user looks at the issues history and sees the importer mentioned as the creator while marking he created the issue a long time ago rather than the day the issue was imported.
Steps to Reproduce
- Create a new JSON or CSV file that matches requirements JIRA expects.
IssueType, Summary, FixVersion, FixVersion, FixVersion, Component, Component, Issue ID, Parent ID, Reporter Bug, "First issue", v1, , , Component1, , 1, , jbloggs Bug, "Second issue", v2, , , Component1, Component2, 2, , fferdinando Bug, "Third issue", v1, v2, v3, Component1, , 3, , fferdinando Sub-task, "Fourth issue", v1, v2, , Component2, , , 2, jbloggs
- Import the file to the target JIRA instance via external system import.
- On completion, access the issue imported via the Issue Navigator page.
- Go to history tab.
Expected Result
JIRA does not show the importer as the issue creator especially not specifying the create date as actual date issue was created if it was specified in the CSV.
Actual Result
JIRA shows the importer as the issue creator and specifies the created date as the date issue was originally created if it was specified in the CSV.
Attachments
Issue Links
- relates to
-
JRACLOUD-62308 JIRA shows Issue Importer as Creator
- Closed