Tempo Ideas

Overview

The Sync Plans with Jira Issues option provides a two-way sync between Tempo Planner and Jira. When enabled, creating new issues in Jira can automatically create new Tempo plans; changing synced Tempo plans will update their related Jira issues, and changing Jira issues will update Tempo plans. Synchronizing the issues from Jira to Tempo is a really powerful integration allowing the option to maintain both Jira and Planning by Tempo aligned, although it has not flexibly to update the worklogs patterns.

Scenario

• The estimated effort of the Jira issue (issue A) is 10 days.

• It is planned to start from Monday 1st April 2024 and finish on 26th April 2024 (elapsed time 20 days)

• It is allocated to a full-time resource (8 hours a day, 5 days a week)

• The resource if fully allocated to another issue (issue B) the week commencing 8th April 2024, which means they will complete the work of Jira Issue A over the elapsed time of 20 days but will not work on it during the second week of April because they will be busy in issue B.

Current behavior

Currently when plans are automatically created in Tempo by Jira issues the hours of the worklogs are by default evenly split across the days. This will mean that during the second week of April the resource will show an overallocation (60h when their work schedule is only 40h)

Desired behavior

The desired behavior will be to allow the spread of the hours of Issue A to show that the resource will not work on Issue A for week 8th April (because they will be working on Issue B) and that will therefore work more hours on Issue A the remaining weeks to complete the tasks. This will therefore not show and overallocation on week commencing 8th April 2024.

The start date, end date, total effort and resource does not change, but the spread of the hours across the period does.

In the example the desired outcome would be: