Knowledge Base Articles
Breadcrumbs

Logged time on sub-tasks not always properly rolling up to parent Epic

This article is for Cloud.

Problem

After logging time on sub-tasks, the worklogs sometimes doesn’t appear correctly related to the Epic they belong to in Reports.

Answer

In this case, there are no problems with worklogs synchronization. This mismatching of relationship can happen if a work item that is related to an Epic has worklogs and it was converted to a sub-task using the function “Convert to sub-task”.

This is a known bug from Jira side where the Jira Webhook we are using does not trigger the “Convert to subtask” work item operation despite being configured to listen to the work item update event. This is the bug’s link: https://jira.atlassian.com/browse/JRACLOUD-74083.

There are three options of Workaround for this problem until we have a fix from Atlassian:

  1. Re-link the sub-tasks to their parent work item:

  • Identify through the Report which are the sub-tasks that are not properly linked with their respective Epic.

  • Open the parent work item from these sub-tasks and re-link it.

  • Pull the report again and check the behavior.

2. After using the function “Convert to sub-task”, re-link the sub-task to its parent work item.

3. Stop using the function “Convert to sub-task”.


.jira-issue { padding: 0 0 0 2px; line-height: 20px; } .jira-issue img { padding-right: 5px; } .jira-issue .aui-lozenge { line-height: 18px; vertical-align: top; } .jira-issue .icon { background-position: left center; background-repeat: no-repeat; display: inline-block; font-size: 0; max-height: 16px; text-align: left; text-indent: -9999em; vertical-align: text-bottom; } TCS-32183