Hello,
the approval reply via email doesn't follow the convention you are mentioning.
Maybe there is a confusion between the approval via comment (NAC) and the approval via email.
The Nac was introduced to meet the requests of some customers needing to approve/reject via the Customer Portal and not via email. In this scenario, it is expected that the comments added to approve/reject the ticket include the worflow transition.
The approval reply via email does not require you specify the workflow transition.
It is expected that the approval reply via email follows the convention below:
The approver can APPROVE/REJECT just replying to the received email by adding the following tags:
Moreover what you add after the previous tag is considered as an approval/rejection comment.
It's required that you always apply the tag @ to end your reply.
The screenshot below provides an example:
EmailReply.jpg
Concluding, the email reply can include additional texts (the approval comment added to the email body will be displayed on the issue Comment tab and/or in the Approval History tab).
Best regards,
Antonella
Hello Antonella,
I created a ticket and received an email that contains the statement below. So I replied to the email with @APPROVED along with my email signature. The comment section on the ticket was populated with the email i sent but it didn't changed the approval status to approved. Is there any settings that I may have missed?
"Approve or Reject by replying to the received email and writing in the email's body @APPROVED or @REJECTED . Optionally, add a comment on a single or on multiple lines. Always apply the tag @ to end your reply."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Page https://chicago.herzum.com/confluence/display/HAP/HAP+-+Mail+System+Configuration illustrates the expected Mail System Configuration.
Can you please confirm that you have chosen the "Approval Mail Handler" as Handler Type?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Below is my "Approval Plugin Mail Handler" setup. My JIRA version is v6.4.12.
Handler Name / Type = Approval Plugin Mail Handler
Server = <our Mail server>
Project = <blank>
Issue Type = <blank>
Properties = Unknown
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you please let me have a screenshot of the comment added to the issue?
E.g.
APPROVED.PNG
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you please let me have a screenshot of the incoming mail setting?
E.g.
MailHandlers.PNG
I suspect that other mail handlers don' t allow the Approval Mail Handler working properly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I figured out the problem and it concerns the existing email account set in my JIRA(jira@travelzoo.com). After creating a unique email address (jira_approval@travelzoo.com) strictly for Approval purposes only, I now have a new problem I encountered.
Issue;
After creating an ticket, an email is sent out to request approval but the "From" address is still jira@travelzoo.com instead of jira_approval@travelzoo.com. This causes the @APPROVED to fail.
Can you also tell me what is the purpose of "Forward Email" from mail handler settings?
image2016-2-24 18:6:37.png
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I found the solutions to may latest issue. I changed the email address from the my project's notification scheme. Thank you for your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Following, some recommendations respect to the email addresses used on your mail server setup and information regarding the Approval Request/Reply email handling.
I hope it helps.
Recommended:
the Username set on the mail server must differ by any Approver email address.
Recommended:
*the Username setup on the IMAP Mail Server must be the same Username set on the mail server SMTP Host.
The Forward email address is not managed by the add-on jet also if it is required when configuring the Approval Mail Handler.
It is a bug we have already planned to fix in our next major release.
In JIRA it is used when a mail handler is unable to handle an email message by forwarding this email message to the email address specified in this field.
Recommended: in order to allow the mail handler working properly, the emails incoming to the SMTP Host email address must not be open because the mail handler is able to handle the new (still not read) incoming email exclusively.
Further Notice
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for responding. Do you know when this bug will be fixed? Is there any workaround while waiting for the fix? This is bug will actually have a major affect in my JIRA environment.
The Forward email address is not managed by the add-on jet also if it is required when configuring the Approval Mail Handler.
It is a bug we have already planned to fix in our next major release.
In JIRA it is used when a mail handler is unable to handle an email message by forwarding this email message to the email address specified in this field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hello, do you have any new update with regards to the Forward Email bug? Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, I don't have an estimate.
It will be fixed close to v. 4.0 release that is currently under planning and design.
Best Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.