The priority labels in use

GET

/v1/requirements/priorities

const url = 'https://beta-api.plune.ai/v1/requirements/priorities';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://beta-api.plune.ai/v1/requirements/priorities \
  --header 'Authorization: Bearer <token>'

The distinct priority labels of the project’s live requirements with how many requirements carry each, the most used first, at most 20. Labels that differ only in case are one (the spelling shown is the first in alphabetical order). ?q= keeps the labels containing that text (case-insensitive). For the Priority filter and the suggestions in the requirement form. Any member reads, a reader too.

Authorizations

bearerAuth
cookieAuth

Parameters

Query Parameters

string

Responses

200

The labels

application/json

object

priorities

required

Array<object>

<= 20 items

object

label

required

string

<= 40 characters

count

required

integer

Example

{
  "priorities": [
    {
      "label": "Must-have",
      "count": 12
    },
    {
      "label": "Should-have",
      "count": 5
    }
  ]
}

401

No / invalid token or session