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; } } }

Time Tracker to trigger external system and wait for reply

Stephan Gspandl

I am using JIRA Cloud and have to achieve the following:

I have to transfer time bookings to another system (ERP) and wait for validation from that system. So, if someone books 1 hour on a story in JIRA, this 1 hour should also be reflected in my ERP. The catch is that ERP also validates the time booking and might reject it due to some accounting issues. In that case, JIRA would have to cancel the booking as well, so JIRA would have to wait until ERP replies.

Is there a possibility to achieve this with JIRA Cloud? Writing a custom app would not be a huge problem, if that's necessary. Any help would be very much appreciated.

Accepted answers

Qu3ntin

Hi,

When you speak about time booking, I assume you speak about worklog (time tracking).

This kind on interface should be doable by API:

If you are using tempo, it seems good
If you are using the JIRA feature, you can not update a worklog. However, you could comment the issue to request a manual update.

All comments

Qu3ntin

Hi,

When you speak about time booking, I assume you speak about worklog (time tracking).

This kind on interface should be doable by API:

If you are using tempo, it seems good
If you are using the JIRA feature, you can not update a worklog. However, you could comment the issue to request a manual update.

Stephan Gspandl

Hi Quentin, thanks for your reply!

So I looked into this, it seems like I can delete worklogs via the REST API, however I'm still looking for a way to have some sort of precondition or validation step before actually changing worklogs or editing an issue. The reason is that once accounting has approved our timesheets, we would not have the permission to change the matching JIRA issues and their worklogs. So if a user tries to edit a JIRA issue in "lock-down", he should get an error message and the issue should stay untouched.

Any idea whether that's anywhere near possible? Thanks again for your help

Qu3ntin

Hi,

I think you could use your workflow for this.

Create a status "Lock-down" and use the solution describe in this topic.

In your API call, just change the status of your issue to Lock-down.

And get it back to In progress (Or any wanted status) when edition can be allowed.

Stephan Gspandl

I'll try that, thanks very much!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud