Tempo Ideas

When you either use the UI or the REST API (https://api.tempo.io/4/plans) the start time of a plan should be considered.

Suppose you have a work item that takes 10h, and you plan it on 23:00, the plan is split into two and on each day 5 hours will be planned, while in fact you only want to plan for 1 hour on the first day and 9 hours on the next.

If you consider the next payload for the forementioned endpoint you will get the attached plan

{

"assigneeId": "60ad32ec411c2200684cd355",

"assigneeType": "USER",

"description": "On call",

"effortPersistenceType": "TOTAL_SECONDS",

"startDate": "2025-11-17",

"endDate": "2025-11-18",

"startTime": "23:00",

"includeNonWorkingDays": true,

"planItemId": "66000",

"planItemType": "ISSUE",

"plannedSeconds": 36000

}

In the picture you see 5h planned on each day, and the end time is also incorrect (should be 05:00)

So I propose to add another efforPersistenceType called 'continuous' which will take the start time and the time left on that day into consideration.

2025-10-31 16_1...

Attachments Open full size