nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Tempo API extracts stopped working , Using Bearer Authentication

Darryl Frittelli

Noticed the Jira Admin , settings , API screen change addtional of Organisation ID ?

Has something changed ?

Example

https://api.tempo.io/core/3/worklogs/project/AAA?offset=0&limit=1000&from=2020-01-01&to=2020-12-10

Accepted answers

Darryl Frittelli

See the example i provided , when excuted through the WeB Browser data was returned successfully up and till the weekend . I now get an 401 Authentication Error . I have been using Bearer authentication in the headerr record. So when i checked to see what had changed on Jira , i noticed that there is now an addiotnal fileld that has been added in the Tempo setting API screen called: OraginsationID , not sure if there is now new rules that need to be applied

All comments

Alexander Eck [Tempo]

Hi @Darryl Frittelli

what do you mean exactly? Any more details you can provide?

Darryl Frittelli

Found the problem had to re-add a new token in tempo API intergation screen .

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud