Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,281
Community Members
 
Community Events
176
Community Groups

Tempo Cloud API only returns current user worklogs

By calling this https://api.tempo.io/core/3/worklogs?from=2020-11-01&to=2020-11-03

It returns my current user.

I don't know if it returns the current Windows user, because in the browser, I was logged to the Atlassian website with the user who has all access.

In the previous questions, like this one: https://community.atlassian.com/t5/Answers-Developer-Questions/Tempo-API-how-to-get-all-worklogs-for-all-users-and-projects/qaq-p/476409

It says to use the Tempo Servlet. However, according to https://tempo-io.atlassian.net/wiki/spaces/CLOUDNEWS/pages/501907993/2019-11-19+Decommissioning+the+Servlet+API+for+Tempo+Cloud+Products .

"Tempo has deprecated the Servlet API for all of its cloud products and will decommission it on April 1, 2020"

Btw, the call works in a docker container.

How can I make it work on Windows 10 (retrieving every worklogs)? What type of login is used in background to retrieve my worklogs? 

1 answer

1 accepted

0 votes
Answer accepted

Hi Jessica,

the worklogs that are returned depend on the permissions of the Bearer token that you use for authentication. A personal Berar token can never have more permissions that it has in Tempo. Means when you can´t see a worklog within the UI you won´t get it from the Tempo API. 

So you should consider to get a personal Bearer token from an admin user or create/use a machine-to-machine token that overrides all permission checks. You should refer to our documentation here

BR

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events