-
Bug
-
Resolution: Obsolete
-
Low
-
18
-
Minor
-
2
-
Issue Summary
Currently, the CSV export uses username information in user related fields (see JRACLOUD-72088).
When you remove an user, it turns it as an inactive user instantly, and its information will be converted to "removed..." in the database due to GDPR:
Problem is that, even though you re-invite the same user (with the very same email address), Jira will map it back to the previous existing user, but the user related information will still be displayed as removed in the CSV export:
Steps to Reproduce
- Invite a user (e.g. example@example.com);
- Set that user as assignee and/or reporter in an issue;
- Remove the user via site administration;
- Export that issue to CSV;
- User will be displayed as "removed...";
- Invite the user (very same email address) back;
- Export that same issue to CSV again.
Expected Results
User related information will reflect the current active user.
Actual Results
User related information will be displayed as "removed...".
Workaround
None at the moment.
- relates to
-
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-77927] User displayed as removed in CSV exports even though it is active
This affects my team and the clients we support.
Reports extracted as CSV are not populating assignee names. This has caused complaints from multiple clients, who are having to manually correct the "removed users".
Please fix this issue asap.
Thanks,
Reuben
**
This affects my team.
This is problematic. Reports on resource's performance based on completion of tickets is a very basic requirement and yet this issue is a total hindrance in showing a comprehensive and accurate report.
This is a big problem for me. I used to export from Jira and copy into an excel file to create easy reports with formatting that I needed. After migrating from server to Cloud and encountering this issue, I need to manually edit to correct the "removed" users. Very frustrating.
This affects my team too.
Jira Cloud
Export in CSV, RSS, or XML format
fields with user info: Assignee and Reporter
1) "removed3" instead of the username
2) "admin" instead of the username of the user that has administrative priviledges.
The information are correctly displayed on the Issue Navigator; but when I export those results on CSV format, for example, the usernames of the users, that I reactivated recently, are masked with the values "removed<ID>" or "<admin>".
All the project managers and other roles complain the extra work on the CSV/XML file! Nowdays the exported files are useless because many username are hidden by those placeholders ("removed<ID>" or "<admin>") and it's impossible to show the results on an audit or evaluate the user performance...
@Atlassian: fix it quickly, please!!!
@Users: Can we anyhow get more pressure on this issue? Write a comment on the impact this bug has on your business, please!
Giulia
This affects my team.
When exporting from Jira Cloud to CSV, RSS, or XML, username fields display "removed15" instead of either the user NAME or ID.
For example, user "ExampleUser" was removed from the organization in "Manage Users". Then I re-invited them. ExampleUser logged in and is working normally in Jira. Now, however, in all CSV, RSS, or XML exports, ExampleUser's name displays as "removed15" in all user picker fields.
This affects all linked data in exports and PowerBI.
Please fix.
Mark
Closing the ticket as we are not able to reproduce this bug anymore.