BigGantt issue affects timeline of old epic

Florian Schatz December 2, 2021

We have setup biggantt with default task structure epic > story/task

and have setup auto-bottom-up for all tickets including epics

If I remove a ticket from an epic, the timeline of the entire epic is still moved depending on the new timeline of the issue (although there is no visible connection), adding the ticket to a new epic now moves both Epics.

I have tried to clear the cache of the plugin, but nothing works.

Only solution we have found is deleting the old issue and creating a new one, but this is not a feasible solutions in some cases.

Thanks for any advice or hints.

2 answers

1 accepted

0 votes
Answer accepted
Anna-BigPicture
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
December 3, 2021

Hi @Florian Schatz

In Auto-bottom-up mode parent task adjusts automatically to its children duration. However, after nesting a task under a new epic, the Start & End dates of the old one should not be affected. 
 
Could you please reach our Technical Support via Service Desk, so our product expert and developers investigate your instance individually?
 
BigPicture Team will gladly help you to resolve the problem.
0 votes
Florian Schatz December 9, 2021

For others experiencing the same problem:

The ticket was part of two programs, so for some reason the second program still kept the old hirarchy. As soon as I made a data sync for the second program too, the problem was gone.

Thanks to the support of BigPicture for this hint.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events