Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

When replacing parameters indicated by <PARAMETER_NAME>, be sure to remove the ‘<' '>’ characters as well.

For example:

  • <MY_API_KEY> replaced by CT_API_xxx

  • <active_only> replaced by true or false

Authorization

Note

...

Navigate to Capacity Tracker configuration screen (Jira settings > Apps > Capacity Tracker).
Create a new API Key, and save it somewhere. For security reason, we will not be able to give it back to you if you lose it.

You can now call the different API endpoints with your API Key (replace <MY_API_KEY> with the previously created key).

...

languagebash

...

In Capacity Tracker 1.1.30, the API authorization method was changed to use custom API keys in order to consolidate our cloud & DC versions. Unfortunately, this caused some issues on some of our client custom setups (mainly related to SSO).

Starting 1.1.31, we are reverting back to using Basic Auth or Personal Access Tokens for the DC version.

In addition, we are introducing a new Global Permission to control who can use the REST API.

  1. You have two options:

    1. Basic Auth

    2. Personal Access Tokens

Endpoints

Get capacity report

...