Release 62 - 2023-04-06

Jira Release 62

April 6, 2023

• AA-3923 RITM2777473 - New date field for Business Technology Release Plan project

• AA-4143 RITM2798933 - Remove Fields from Screens in Business Technology Release Plan project

• AA-3412 RITM2723304 - Restrictions on Planned Dates on Changes

  • Planned Start Date cannot be after Planned End Date

  • If Date fields are edited and Planned Start Date is after Planned End Date, Planned End Date will be cleared and a comment added

  • If Planned Start or End Date is edited/updated after the Change is in Authorize status, the update will be reverted to the previous values and a comment will be added

AA-3923

Add new screen scheme “DRPL Epic Screen Scheme 2.0” - issuetype screen scheme “DRPL Issue Type Screen Scheme 2.0“

Verify custom field “Forecasted Delivery Quarter” shows only on Epics

AA-4143

Update screen scheme “DRPL Issue Type Screen Scheme 2.0“

Verify custom fields “Priority” and “Impact Score” were removed from create screen for Epic

Verify “On Hold Reason” custom field is removed from “Initiative” issuetype

AA-3412

Restrictions on Planned Dates on Changes:

• Planned Start Date can’t be after Planned End Date

• Planned Start/End Dates cannot be updated after in Authorize status.

Update Exalate Connection CHGJira_to_CHGSNow for Planned Start/End Dates

//Planned Dates
//debug.info("replica.customFields.'Planned Start Date'?.value is ${replica.customFields.'Planned Start Date'?.value}")
TimeZone.setDefault(TimeZone.getTimeZone("UTC"))
import java.text.SimpleDateFormat
//def starttimestamp = (replica.customFields."Planned Start Date"?.value)
//def endtimestamp = (replica.customFields."Planned End Date"?.value)
sdf = new SimpleDateFormat("MM-dd-yyyy HH:mm:ss")

//Start Date
def starttimestamp = (replica.customFields."Planned Start Date"?.value)
def starttargetDate
if (replica.customFields."Planned Start Date"?.value)
{
starttargetDate = sdf.format(replica.customFields."Planned Start Date"?.value)
//debug.info("starttargetDate is ${starttargetDate}")
}
//debug.info("entity.start_date is ${entity.start_date}")

//End Date
def endtimestamp = (replica.customFields."Planned End Date"?.value)
def endtargetDate
if (replica.customFields."Planned End Date"?.value)
{
endtargetDate = sdf.format(replica.customFields."Planned End Date"?.value)
}
//debug.info("endtargetDate is ${endtargetDate}")

//Only populate Plannned Dates if Planned End Date is not empty and is greater than Planned Start Date
if (endtargetDate != "" && endtargetDate >= starttargetDate)
{
entity.start_date = starttargetDate
entity.end_date = endtargetDate
}
else
//Clear Planned End Date and set Planned Start Date
{
entity.end_date = ""
entity.start_date = starttargetDate
}

COMPLETED

Action 1 - “End Date cleared if Start Date is greater” JMWE Event Based Action

Event:

Trigger: Issue Field Value Changed

Field to monitor: Planned End Date, Planned Start Date

Scope:

Projects: All Projects

Issue types: Change

Only apply to issues that match a JQL filter

Issuetype = Change and status not in (Authorize, Scheduled, Implement, Review, Closed, Canceled)

Only apply to issues that match a Nunjucks condition:

User is not Exalate and Planned End Date is not empty and Planned Start Date is greater (later) than Planned End Date:

{{user.accountId!="557058:c020323a-70e4-4c07-9ccc-3ad89b1c02ec"}}
&&
{{ issue.fields.customfield_10081 is not null }}
&&
{{ issue.fields.customfield_10080 >issue.fields.customfield_10081}}

Post Function 1 - Display Message to User

Title: Planned End Date Validation

Content: Planned Start Date cannot be after Planned End Date.
Planned End Date is cleared.

Message type: error

Conditional execution:

{% if issue.fields.customfield_10080 > issue.fields.customfield_10081 and issue.fields.customfield_10081.length > 0 %}
Start is greater than End
{% endif %}

Post function 2 - Clear fields

The following fields of the current issue will be cleared: Planned End Date
Run as add-on user.

Run this post-function conditionally:

{% if issue.fields.customfield_10080 > issue.fields.customfield_10081 and issue.fields.customfield_10081.length > 0 %}
Start is greater than End
{% endif %}

Post function 3 - Comment on issue

Comment issue(s)

A comment will be added to the current issue with the following text:

Planned Start Date was updated and was after Planned End Date. Planned End Date field was cleared.

COMPLETED

Action 2 - “Change Date after Authorize” JMWE Event Based Action

Event:

Trigger: Issue Updated

Scope:

Projects: All Projects

Issue types: Change, Change Task

Only apply to issues that match a JQL filter

JQL expression:Issuetype = Change and status in (Authorize, Scheduled, Implement, Review)

Only apply to issues that match a Nunjucks condition:

User is not Exalate:

{{user.accountId!="557058:c020323a-70e4-4c07-9ccc-3ad89b1c02ec"}}

Post Function 1 - Set issue fields

For the current issue

Planned Start Date will be set to:

{{ context.changelog.fields["customfield_10080"].from | date ('x')}}

Post Function 2 - Display Message to User

Title: Planned Date restricted once approved

Content: Updates to Planned Start and Planned End Dates are not allowed after Change is in Authorize status.

COMPLETED

Update Change Workflow to include planned dates validator

COMPLETED

Verify Start Date can’t be after End Date when creating a Change.

COMPLETED

Verify Start/End Dates can’t be changed after Authorize status.

COMPLETED