-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
None
-
10
-
Severity 3 - Minor
-
0
-
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Summary
The from name in the reporter email shows Anonymous user when the user has uppercase letter in the username.
Steps to reproduce
- Create Service Desk
- Create admin user with uppercase letters in username (ex. "adminAdchSupport") and assigned Service Desk Team role
- Login in as adminAdchSupport and create a SD request
Expected Results
- The from name in the email should be the reporters full name:
FromName='Jason Worley (JIRA)'
Actual Results
- The from name in the email shows Anonymous (JIRA)
FromName='Anonymous (JIRA)'Log Excerpt
2015-02-09 11:58:00.551425500 2015-02-09 11:58:00,551 Sending mailitem To='jworley@atlassian.com' Subject='(DESK-22) dddaaaa' From='null' FromName='Anonymous (JIRA)' Cc='null' Bcc='null' ReplyTo='null' InReplyTo='null' MimeType='text/html' Encoding='UTF-8' Multipart='javax.mail.internet.MimeMultipart@1eb9cf3' MessageId='null' DEBUG ServiceRunner Mail Queue Service [com.atlassian.mail.outgoing] 250 2.0.0 Ok: queued as 78EA05880186
Workaround
- Rename the reporter to have all lowercase letters. (from example: "adminAdchSupport" to "adminadchsupport"). Now when the reporter creates an SD request the from field is correctly populated with the full name:
2015-02-09 11:52:00.805045500 2015-02-09 11:52:00,804 Sending mailitem To='jworley@atlassian.com' Subject='(DESK-23) dfdfddfd' From='null' FromName='Jason Worley (JIRA)' Cc='null' Bcc='null' ReplyTo='null' InReplyTo='null' MimeType='text/html' Encoding='UTF-8' Multipart='javax.mail.internet.MimeMultipart@1c6e67b' MessageId='null' DEBUG anonymous Mail Queue Service [com.atlassian.mail.outgoing] 250 2.0.0 Ok: queued as C09AF6180FFB
- relates to
-
-
- Closed
-
- links to
- mentioned in
-
Page Failed to load
- was cloned as
-
TESLA-953 Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-1488] Reporter/Service Desk Team
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Labels | Original: affects-cloud affects-server cqt ril | New: affects-cloud affects-server cleanup-seos-fy25 cqt ril |
| Labels | Original: affects-cloud affects-server cqt | New: affects-cloud affects-server cqt ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 954806 ] |
| UIS | Original: 5 | New: 0 |
| UIS | Original: 0 | New: 5 |
| Support reference count | Original: 9 | New: 10 |
| Support reference count | Original: 10 | New: 9 |
| Support reference count | Original: 9 | New: 10 |
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Service Management Data Center