JWT Send an Email Post Function uses the day prior to the date entered in the Create Issue Screen

Issue #859 resolved
Joseph Pursel created an issue

Hi Fidel,

This email produced by the JWT Send an Email post function, shown below, has the Desired United States Launch Date of 28/Oct/17 when the user entered 29/Oct/17 in the create issue screen.

Request number in JIRA: https://company.com/browse/TEST-198 Project Title: PLEASE DISREGARD - TEST 911 Testing

A Change Management 911 request has been submitted by userxyz on behalf of the line of business Other and approved by user@company.com.

  • Project Description: PLEASE DISREGARD - TEST 911 Testing CMPMO-32
  • Impacted Marketplaces: United States
  • Desired United States Launch Date: 28/Oct/17
  • Desired Canada Launch Date:

A screen shot of the dated entered into JIRA is attached. The post function code is below:

The code block below shows the post function content for the Subject and Body.

Subject: Change Management 911 %{00000}

Body:
Request number in JIRA: %{12602}
Project Title: %{00000}

A Change Management 911 request has been submitted by %{00006} on behalf of the line of business %{12471} and approved by %{12510}. 

- Project Description: %{00001}
- Impacted Marketplaces: %{12442}
- Desired United States Launch Date: %{12457}
- Desired Canada Launch Date: %{12460}

customfield_id %{12442} is a Date Picker Custom Field. Also attached is a snap shot of the dates shown in the created JIRA issue.

Issue was created on 10/Oct/17 at 12:30PM US PDT time. JIRA System Time - Default user time zone - (GMT-05:00) Detroit.

Please let me know if you require additional information.

Thank you, Joe

Comments (2)

  1. Fidel Castro Armario repo owner

    Hi @amazonadmin,

    The bug should have been fixed in version 2.2.43_beta_5. Please, try it and let me know whether it solves your problem.

    Thanks

  2. Joseph Pursel reporter

    Hi Fidel,

    I installed the beta and the email dates are correct. Thank you for your prompt response.

    Thank you, Joe

  3. Log in to comment