Fix Version | Jira Release 62 |
---|---|
Release Date | April 6, 2023 |
Change Number (Jira/ServiceNow) |
|
Scope |
|
Change | Description | Status |
---|---|---|
AA-3923 | Add new screen scheme | |
Verify custom field “Forecasted Delivery Quarter” shows only on Epics | ||
AA-4143 | Add new screen scheme | |
| 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:
| |
| Update Exalate Connection CHGJira_to_CHGSNow for Planned Start/End Dates //Planned Dates //Start Date //End Date //Only populate Plannned Dates if Planned End Date is not empty and is greater than Planned Start Date | |
| 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
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:
Post Function 1 - Display Message to User Title: Planned End Date Validation Content: Planned Start Date cannot be after Planned End Date. Message type: error Conditional execution:
Post function 2 - Clear fields The following fields of the current issue will be cleared: Planned End Date Run this post-function conditionally:
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. | |
| 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: 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. | |
| Verify Start Date can’t be after End Date when creating a Change. | |
| Verify Start/End Dates can’t be changed after Authorize status. | |
| ||
|
PASSED
COMPLETED