We have a client where we encountered the following situation: * TEMPO installed, everything is ok, they use the approve timesheet stuff, and status is ok: 'ready' for past time intervals, 'open' for the current, 'approved' & 'rejected' if it was the case * We installed JIRA Agile * TEMPO timesheet status is reset to the 'ready' state for all timesheets, no matter if they were approved or not. For new timesheets, approval works correctly, but for those pre-existent just before JIRA Agile install, it does not work ('ready' status only) We would love to fix this ASAP, does anybody have a clue what's going on there?

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

TEMPO Timesheets & JIRA Agile - Is this the expected behaviour?

Radu Dumitriu

We have a client where we encountered the following situation:

TEMPO installed, everything is ok, they use the approve timesheet stuff, and status is ok: 'ready' for past time intervals, 'open' for the current, 'approved' & 'rejected' if it was the case
We installed JIRA Agile
TEMPO timesheet status is reset to the 'ready' state for all timesheets, no matter if they were approved or not. For new timesheets, approval works correctly, but for those pre-existent just before JIRA Agile install, it does not work ('ready' status only)

We would love to fix this ASAP, does anybody have a clue what's going on there?

Accepted answers

Radu Dumitriu

Mystery solved: never trust an user who says: "I didn't do anything!".

The client actually modified the reporting period (changed the start of the working week from Monday to Sunday). Therefore, all timesheets start date do not match => the behaviour above.

(!and thanks to the TEMPO team for their fast escalation!)

All comments

Jobin Kuruvilla [Adaptavist]

Certainly not the expected behavior. Something else might have happened. You might want to reach out to Tempo support!

Radu Dumitriu

I've done that ... thanks! But I thought that asking around cannot hurt

Radu Dumitriu

Mystery solved: never trust an user who says: "I didn't do anything!".

The client actually modified the reporting period (changed the start of the working week from Monday to Sunday). Therefore, all timesheets start date do not match => the behaviour above.

(!and thanks to the TEMPO team for their fast escalation!)

Welcome!

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

Quick Links

Find more posts tagged with

jira

tempo-timesheets