Jira Tempo API extracts stopped working , Using Bearer Authentication

Darryl Frittelli March 15, 2021

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

 

 

 

 

 

 

2 answers

1 accepted

1 vote
Answer accepted
Darryl Frittelli March 15, 2021

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 

Darryl Frittelli March 15, 2021

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

Like Alexander Eck [Tempo] likes this
0 votes
Alexander Eck [Tempo]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 15, 2021

Hi @Darryl Frittelli

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

BR

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events