How do I stop Epics changing tasks to "done" when the Epic moves to "Done"?

[Gemma FRENCH]

I want to move an Epic to "Done", but there are tasks under that Epic which are not complete (and will not be complete). However, when I have changed the status of the Epic to "Done", all tasks under that Epic move to the same status. 

How do I stop this from happening? 

[Morten Christophersen]

You should separate Status from resolution.

Before closing an Epic everything under it should be taken care of (meaning moved to Closed(Done, is a fix of status and resolution). That is you should make the system to that the Status only reflects the progress of the issue through your step, and then you should update the resolution with the end state. Resolution state examples: unresolved(typically this is until it get to the closed status where any of the other must be chosen), fixed/done, won't fix, duplicate.

If you do it like this then you know if somebody actually took a decision on not doing the issue and not that it was simply forgotten:-)

[Brian Trepto]

Hi @Gemma FRENCH

[Gemma FRENCH]

Thanks Brian. Where I have a day 2 release I move tasks to the relevant parent. However, sometimes I do not have that and completing the epic closes the tasks which we have not released. For example – a bug identified which doesn’t impact the customer and can be fixed at a later date. This will then disappear once the epic is closed.

I have identified under automation that there is a rule to the effect described – thanks for that info.