...
Property Name | Property Code | Required | Description | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Jira URL | FDJIRAITSM_URL | Yes | Jira URL (http://myjira.atlassian.net) | ||||||||||||||
Jira User | FDJIRAITSM_USER_NAME | Yes | Jira User Name | ||||||||||||||
Jira API Token | FDJIRAITSM_API_TOKEN | Yes | API token for Jira Note that encrypted properties are stored in Credential Store (Local or External) and can be configured using Edit button next to credential name drop down. Alternatively, you can reuse single credential for multiple properties also, in which case you should name that credential appropriately. | ||||||||||||||
Jira Ticket URL Pattern | FDJIRAITSM_TICKET_URL_PATTERN | Yes | The URL to open Jira ITSM and navigate to the change ticket associated to the project workflow execution
| ||||||||||||||
Jira GET Rest API Pattern | FDJIRAITSM_TICKET_REST_GET_PATTERN | Yes | Jira Rest API URL Pattern for a GET request
| ||||||||||||||
Jira POST Rest API Pattern | FDJIRAITSM_TICKET_REST_POST_PATTERN | Yes | Jira Rest API URL pattern for creating a change ticket
| ||||||||||||||
Approved Check Script | FDJIRAITSM_APPROVED_SCRIPT | No | A Groovy expressions which determines whether a task for the change ticket is approved or not. The expression must return a boolean, and has access to the following variables:
Default Check
Example that checks custom field value specific to target environment
| ||||||||||||||
Rejected Check Script | FDJIRAITSM_REJECTED_SCRIPT | No | A Groovy expressions which determines whether a task for a change ticket is rejected or not. The expression must return a boolean, and as has access to the following variables:
| ||||||||||||||
Additional Info Script | FDJIRAITSM_ADDITIONAL_INFO_SCRIPT | No | A Groovy expression which determines additional information to add to an external approval when it is approved or rejected. The expression must return a Map<String, String> and have an entry with the key of "notes" for the value to get added to external approval as a task note. Script has access to the following variables:
| ||||||||||||||
Don't poll | FDJIRAITSM_DONT_POLL | No | Disable automatic polling (every minute) of Jira tickets for status changes. The default value is false, which means polling will occur. Only check this box if you are using the FlexDeploy REST API to communicate ticket approval/rejection. |
Jira ITSM Ticket Fields
Within the script properties on the Jira ITSM Instance. The following values are available to you via the TICKET object to use in your script logic. For example, TICKET.project.summary would return the summary of the ITSM change.
Field Code | Display Name | Description | Data Type | Required |
---|---|---|---|---|
fields.summary | Summary | Summary of the change | String | Yes |
fields.project.key | Project Key | Key of project the change is in | String | Yes |
Issue Type | Type of issue for ticket | String | Yes | |
fields.description | Description | Description for the change | String | No |
Priority | Priority of the change | String | No |
...