-
Bug
-
Resolution: Fixed
-
Low
-
3.0.4
Summary:
The Notification Email Subject for comment event only include Issue Key.
Steps to Reproduce:
- Create a Service Desk Project.
- Raise a request as a Customer with a legit Email Address.
- Assign the ticket to an Agent.
- Let the Agent comment on the ticket.
- Wait for the Email Notification to sent to the Customer/Reporter mail inbox
Expected Result:
- The Notification email will include the Issue Key and Issue Summary on its subject.
Actual Result:
- The Notification Email did not include Issue Summary.
Notes:
- Based on the Release Notes there is no statement about the details about Mail Template changes.
- As in version prior to JSD 3.x the summary is included, it could be said that it is a regression for this version.
- There is a customer that rely on the Issue Key and Issue Summary of the Mail Notification to do other operation.
- relates to
-
JSDSERVER-2263 Provide Summary and Description Information in Service Desk Confirmation Emails Sent to Customers
- Closed
-
- Closed
- was cloned as
-
QUALITY-280 Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-3188] Issue Summary missing from the Subject Email Notification
Jouni Jaakkola
added a comment - This is a major issue for our JSD setup. As we are receiving email requests from another ticketing system, losing that system's ticket # in our comment reply email loses the reference to the original ticket #. This is not acceptable - any suggested workarounds? We are currently running the cloud version.
Jouni Jaakkola
added a comment - This is a major issue for our JSD setup. As we are receiving email requests from another ticketing system, losing that system's ticket # in our comment reply email loses the reference to the original ticket #. This is not acceptable - any suggested workarounds? We are currently running the cloud version. 
Hisham Dekmak
added a comment - Anyone is facing the issue JSD-3189 , or it's just me?
None that I know of. I guess we have to wait for
JSD-218or this issue to be fixed! I even asked for the source code so we could fix it (temporarily) ourselfes. But the source code for JSD is not yet availbale either (JSD-397)