-
Notifications
You must be signed in to change notification settings - Fork 0
JIRA plugin
The JIRA plugin provides access to the following Azure DevOps resources:
- Boards, quick filters and issues in a board or quick filter.
- Dashboards.
- Filters.
- Issues.
- Projects.
Besides this, you can also create new items from the tool using the Azure New option. This can create:
- Issues.
- Queries.
Use the configuration screen to setup JIRA environments.
You can setup connections to multiple environments if you have access to more than one, e.g. your company and your personal JIRA environment.
Click Add to add a new connection.
A connection to a JIRA environment requires the following fields to be entered:
- Name of the environment. The name is used to disambiguate multiple environments. It'll be appended to the search category, e.g. "JIRA Issue (pvginkel)". This is only done if you have access to more than one environment.
- URL is the URL to your JIRA environment. This should be something similar to https://yourcompany.atlassian.net/.
- User name & password.
JIRA supports three ways to authenticate, depending on the type of JIRA environment you're connecting to:
-
If you're using JIRA Cloud, you should create an API key to authenticate. You're using JIRA Cloud if your domain name ends in "atlassian.net" like in the example. The documentation page Manage API tokens for your Atlassian account describes how to create one. When using an API token, enter your email address into the User name field and the API token into the Password field.
-
If you're using self hosted JIRA, you have two options to authenticate TQL:
-
You can try using your own password. To do this, enter your user name (likely your email address) into the User name field, and enter your password into the Password field.
-
You can create a PAT token. The documentation page Using Personal Access Tokens describes how to create one. Leave the User name field empty and enter the PAT token into the password field.
-