-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 11.3.5, 11.3.7
-
Component/s: Troubleshooting and Support Tools (ATST)
-
None
-
11.03
-
1
-
Severity 3 - Minor
-
2
Issue Summary
The ATST plugin has a new feature that allows Support Zips to redact sensitive data within the log files.
There are instances where it misses anonymizing usernames in the atlassian-jira-outgoing-mail.log file.
Steps to Reproduce
- Install ATST 3.13.1
- Configure outgoing mail notifications.
- Make a change on an issue to send a notification.
- Generate a Support Zip with Redact data enabled.
- Review atlassian-jira-outgoing-mail.log file.
Expected Results
All usernames should be redacted in the atlassian-jira-outgoing-mail.log file.
Actual Results
Usernames under the reporter and remoteUser fields in the atlassian-jira-outgoing-mail.log file are not redacted:
2026-05-29 20:22:00,065+0000 Sending mailitem com.atlassian.jira.mail.IssueMailQueueItem@5d81a354[issue=com.atlassian.jira.issue.IssueImpl@3136e525[id=10200,summary=Testing,key=redacted-IGTTN-24,created=2026-05-29 19:48:42.675,updated=2026-05-29 20:21:15.897,assignee=redacted-4n9b(admin),reporter=admin(admin)],remoteUser=admin(admin),notificationType=Current_Assignee,eventTypeId=6,templateId=6] INFO anonymous Mail Queue Service [c.a.j.plugin.userformat.DefaultUserFormats] Mapping user format type 'profileLinkExternal' to the default format in module with key 'jira.user.format:profile-link-external-user-format'
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available