Feature - Lifecycle Incomplete although all stages are complete (closed)

I have just completed the first incident within Eramba. The status of the incident is still “ongoing incident” although all stages are “completed”. Is this a bug or does it take some time or a job to update the incident status overall?

Morning !
You need to “close” it (edit and change the status)
We could set an option to “automatically close” when all stages are tagged as completed ?
Esteban

1 Like

Hi

ok. Thanks. Yes, that would be good to set it automatically to close. At least in our environment where only 1 - 2 persons will work on the incident process in eramba.

Logged:

https://github.com/kisero/eramba_v2/issues/453

Thanks again

We are looking at publishing this stuff on the 27th Feb
Cheers