-
Bug
-
Resolution: Fixed
-
Low
-
None
-
1
-
Minor
-
Issue Summary
Non-English characters such as the name of the authentication policies in Organization Audit Logs are garbled.
Steps to Reproduce
- Create an authentication policy with the non-English name (ex. テスト)
- Add a user to the authentication policy created in Step 1
- Go to the audit log page
Expected Results
Audit logs should not contain garbled characters.
Actual Results
See the above screenshot.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
-
- Closed
-
[ACCESS-1319] Non-English language in Organization Audit Logs contains strange characters
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Short Term Backlog [ 12074 ] | New: Closed [ 6 ] |
| Attachment | New: Screen Shot 2022-10-31 at 1.58.11 PM.png [ 429674 ] |
| Assignee | Original: Jack Burgoyne [ 77388d647f98 ] | New: Gaurav Dalvi [ gdalvi@atlassian.com ] |
Atlassian
There are some size limitation of Audit log that user can download, this BUG is more serious in Non-English users.
| Status | Original: Needs Triage [ 10030 ] | New: Short Term Backlog [ 12074 ] |
| Assignee | New: Jack Burgoyne [ 77388d647f98 ] |
| Support reference count | New: 1 |
| Description |
Original:
h3. Issue Summary
Non-English characters such as the name of the authentication policies in Organization Audit Logs are garbled. !AtlassianSupport 2022-09-14 at 11.39.55.png|width=556,height=395! h3. Steps to Reproduce # Create an authentication policy with the non-English name (ex. テスト) # Add a user to the authentication policy created in the step 1 # Go to the audit log page h3. Expected Results Audit logs should not contain garbled characters. h3. Actual Results See the above screenshot. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
Non-English characters such as the name of the authentication policies in Organization Audit Logs are garbled. !AtlassianSupport 2022-09-14 at 11.39.55.png|width=556,height=395! h3. Steps to Reproduce # Create an authentication policy with the non-English name (ex. テスト) # Add a user to the authentication policy created in Step 1 # Go to the audit log page h3. Expected Results Audit logs should not contain garbled characters. h3. Actual Results See the above screenshot. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
As an audit log platform team, we decided in the beginning, the main design principle while developing this platform, that audit logs will be immutable and we don't want to develop functionality to alter those audit logs once they are set in the system. This is for compliance and security reasons you don't want anybody to modify the audit logs once they are generated. Hence we don't have a plan to develop a way to alter them. Therefore, unfortunately, those garbled characters can not be fixed. We apologize for this inconvenience.
We have tested that newly generated audit logs are not having the issue of separate characters. This was caused only during the incident and after that, we don't see the problem.
3fb4e7e36438 : Please feel to ping us if you see such an occurrence in the future. As of now please feel free to close this ticket.