Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
on
12-07-2021
04:40 PM
- edited on
12-07-2021
05:11 PM
by
Claudia.Landiva
This article starts with describing integration between the Controller and JIRA, step-by-step. Then, it describes the workflow between the Controller and JIRA. JIRA integration allows the Controller to automatically create a JIRA issue. When an event is triggered in the Controller, it triggers a custom HTTP action that creates a new JIRA issue.
The OAuth 2.0 Authorization Code method is described in the OAuth Community.
NOTE | The ticket creation and synchronization via JIRA Action may not work if your JIRA instance includes customizations, such as custom mandatory fields
The credentials you will need to configure the JIRA-Controller integration include user authorizations, installation paths, server names, and more, listed below.
Controller parameter settings |
|
PARAMETER |
VALUE INPUT |
Controller Host |
myController |
Controller Port |
8090 |
Application Name |
AppDynamics |
Consumer Key |
Copy from the JIRA Integration page |
Consumer Name |
<Controller Host>:<Controller Port> |
Public Key |
Copy from the JIRA Integration page |
Controller Username |
admin |
Controller Password |
Consult operational manual |
Application ID |
<The Application that controls notification> |
JIRA parameter settings |
|
PARAMETER |
VALUE INPUT |
JIRA_Username |
<AppD Connector Username> |
JIRA_Password |
Consult operational manual |
The required parameter data are gathered during the integration. No additional steps are needed to prepare the Controller for JIRA integration configuration.
In order to establish that incoming event data will be rerouted to the correct JIRA location (support individual, support group, etc.), an authorized user must be created on the JIRA instance. In principle, the more application rights the JIRA user has, the more he can execute on the system.
There is no required naming convention.
To access the JIRA integration page, click Settings > Administration > Integrations.
Then go to Atlassian JIRA OpenAuth (labeled 4, in the screenshot below) to access the JIRA Integration page”.
NOTE | Don’t include the leading HTTPS:// protocol string
A green checkmark below the Continue button confirms that JIRA connectivity has been established.
Execute the following steps on the JIRA instance.
Check to see whether the authorization link has been verified by looking for the GREEN checkmark shown under “Create an Application Link in JIRA”
With the JIRA integration successfully established, proceed to create Actions.
Next, create the JIRA Action.
The integration only supports 4 out-of-the-box attributes for JIRA ticket creation:
NOTE | Clearly, this is a newly created JIRA SaaS configuration. Once you apply customizations on JIRA, while the JIRA Integration will work as described above, the ticket creation and synchronization via JIRA Action may not work.
For example, this integration does not work with a custom mandatory field in JIRA
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form