...
Preparing for JIRA ITSM Integration with FlexDeploy
...
You need to create an API token for use in FlexDeploy. The API token will be encoded using base64 before used in the request to get change request or create any new request
Log into Jira ITSM
...
Go to Account Settings
Click Security
Click Create and Manage Tokens
Here, you can create a new API token, and use this token for your Jira ITSM instance in FlexDeploy.
...
Permissions
The user configured in FlexDeploy must have permission to access and create tickets. You can view and update permissions for your Jira ITSM project from Project Settings → Permissions.
...
Jira ITSM Instance Properties
Property Name | Property Code | TypeRequired | Description | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Jira URLString | FDJIRAITSM_URL | Yes | Jira URL (http://myjira.atlassian.net) | ||||||||||||||
Jira UserString | FDJIRAITSM_USER_NAME | Yes | Jira User Name | ||||||||||||||
Jira API TokenString | 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 PatternString | 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 PatternString | FDJIRAITSM_TICKET_REST_GET_PATTERN | Yes | Jira Rest API URL Pattern for a GET request
| ||||||||||||||
Jira POST Rest API PatternString | FDJIRAITSM_TICKET_REST_POST_PATTERN | Yes | Jira Rest API URL pattern for creating a change ticket
| ||||||||||||||
Approved Check ScriptString | 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 ScriptString | 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 ScriptString | 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 pollBoolean | 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. |
...