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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Delete all Tempo worklogs from an issue using Jira Automation and Tempo's REST API

In this article I present a solution to delete all Tempo worklogs from an issue, using Jira Automation and Tempo's REST API. The reason for creating this article is because I've got a follow-up question on my previous article. So.. let's get this!






Tempo Timesheets

Project Permissions

  • Browse Project
  • View all worklogs
  • Delete all worklogs

User profile

Project or Jira admin and above

Tempo REST API endpoints

Get worklogs from an issue


Delete worklogs


Rule description

This rule delete all Tempo's worklogs from an issue. Keep in mind that Tempo has a way of deleting all worklogs from a project, but this rule doesn't do this.



  • Create a Tempo API token

    • Go to Tempo>Settings,
    • Scroll down to Data Access
    • Select API integration



This rule has again pretty easy steps:

  • Manual trigger (or a trigger of your choice)

  • Send a web request to get all Tempo worklogs of the issue

  • Branch to run for every Tempo worklog using smart values

    • Delete a specific Tempo worklog



Rule Breakdown

Now let’s break down the rule:


🔫 Trigger

For the trigger I went with manual rule, since I wanted to have complete control of when the rule will run. Of course fill free to adjust the trigger to be run only by a selected group. Since this rule was on my test instance in which I am the sole user, I left it blank:

worklogrule001 trigger.png

💡 Get all worklogs

The first component, after the trigger, is the “Send web request” component.


As a web request URL we enter the following URL, based on the first REST API endpoint:{{}}

Tempo's base API URL is currently So after the base url, we use the first endpoint, which is to get all Tempo's worklog /worklogs/issue/{id}. We replace {id} with the {{}} smart value so this rule can work on all issues to which we decide to run it. In addition we add as headers:

  • Content-Type ↔︎ Application/JSON

  • Authorization ↔︎ Bearer TEMPO_API_TOKEN

On authorization, you will enter as a value the word “Bearer” followed by the API token which we acquired from the “Prerequisites” section.

As the http method, we use “GET”, we leave the body as EMPTY and we make sure to check the “Delay execution of subsequent rule actions until we've received a response for this web request”. We can also validate the request if we click on the “Validate your web request” expand section and type an issue key.


✒️ Audit Log (optional)

I inserted a Log component just to make sure that I'm getting the correct worklogs IDs. To do that, I used the smart value


which yields the tempo worklogs IDs.


🔀 Advanced Branching

The GET request from the previous web response will return a payload which we can further manipulate using the smart value {{webResponse}}. To be able to delete the worklogs it is imperative to know the worklogs ids. To do that we will use another smart value on the Advance Branching component:



This advanced branching is different than the one from my previous article, since it's not imperative to split the values. We save the above smart value as tempoWorklogID (or a name of your preference).


❌ Delete each worklog

Next we add another “send web request” component.


As a web request URL we enter the following URL, based on the second REST API endpoint:{{tempoWorklogID}}

We use the {{tempoWorklogID}} smart value which was constructed on the Advanced Branching component. Like before, we populate the headers accordingly:

  • Content-Type ↔︎ Application/JSON

  • Authorization ↔︎ Bearer TEMPO_API_TOKEN

As the http method, we use “DELETE”, we leave the body as EMPTY. You can again validate the request if you click on the “Validate your web request” expand section and type an issue key.


💰 A Penny For Your Thoughts

So that's it! That's the way to delete Tempo's worklog from an issue. Do you have any thoughts? Let me know if the comment section!

1 comment

Hey @Alex Koxaras _Relational_ 

I have to edit my previous post, because I had an error somewhere in my automation that I got corrected now. This example works just fine.

For me, I am combining the infos from you and from @Susanne Götz _Tempo_ here: 

Add worklog description and time spent as comment to the issue - Knowledge Base Articles - Confluence (

which is helping me a lot! Both of your support is highly appreciated 😊

Thank you.

Cheers, Alex


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events