Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

2. On the right of the toolbar, click the Configure Data Sources icon. The data sources configuration opens.

...

3. In the Data Sources Configuration window, in the Data Sources tab, select JIRA. The Step 2. Configure Source pane opens.

...

4. On the Step 2 pane configure JIRA Data Source.

...

1. Configure credentials

There are 3 options of Jira integration:

...

  • Access token - In order to use OAuth 1.0 with Jira in Perf, you will need to obtain an Access Token from Jira and provide it to Perf as part of the data source configuration settings. Click “Get Token” and follow instriction.

  • Private Key - generated a public-private key pair (see Jira guidline).

  • Consumer Key - is a unique identifier assigned to a client application by Jira during the registration process.

...

1.3 OIDC authentication

The following information must be provided:

...

Expand
titleAdditional Info & Troubleshooting

JIRA Cloud vs. Server

JIRA Cloud

If you use JIRA Cloud (for example, https://<your-subdomain>.atlassian.net), follow the rules:

  • Use your e-mail address (i.e. with “@”) in credentials here. Pure login (i.e. without “@”) will not work due to improvements in authentication by Atlassian (link).

  • Use API Token instead of a password, tokens are more secure and you can manage them here
    For more details see How to manage your API Tokens in JIRA.

JIRA Server

If you use a JIRA Server, use a regular login and password.

CAPTCHA

After several unsuccessful attempts to log in, JIRA refuses all subsequent attempts without passing the CAPTCHA challenge. 

To resolve the persistent CAPTCHA:

Default credentials

If you enter an URL that coincides with any URL from Default Credentials, no password/login is needed. For more information, see PERF Administration.

Check connection

...

2. Workflows Interpretation

Workflows represent processes on your project and give you control over the project's progress. PERF simplifies workflows by distributing each of them into three different buckets.
At this step issue statuses pulled from a JIRA project are to be distributed into 3 buckets: To DoIn Progress, and Done.

  • To Do: for statuses meaning the item is not ready for development.

  • In Progress: for statuses meaning the item is in development.

  • Done: for statuses meaning the item satisfies the "Definition of Done" criterion in a project.

...

Change is applied immediately, data load is unnecessary.

For more details, see Include Sub-Items into Metrics Calculation.

...

3. Configure fields mapping

Custom fields in Jira enable collecting additional information not available in the default system fields. 

PERF allows using custom fields: 

  • to calculate metrics with custom fields (e.g., story points estimations, person-hours estimations, severity, priority, etc.);

  • to build custom metrics over the data collected in the custom fields;

  • to use custom fields in PERF and make accurate calculations, defining where the project saves the required data.

To map metrics attribute with custom fields, select the needed attribute in the table and choose the corresponding custom field. Otherwise, PERF will use a standard system field for the parameter.

...

If you plan to build custom metrics over data with custom fields, we recommend adding required custom fields to the table to be available in the "Fields" tab of advanced custom metrics.

...

Info

If a custom field’s value is longer than 500 symbols, then PERF will save only 500 symbols.

...