Severity not retained after issue is closed


I am wondering why you would not show issue severity for closed issues. In our organization, we need to collect metrics for each release, which includes number of critical, severe, normal, minor issues fixed in the release. It would help if I can see the issue severity even after the issue is closed.


Statement from Kunagi Team

Kunagi will now show the severity for closed Issues.


Issue is closed for Release 0.24.4.


Thu, Jan 3, 2013, 11:31 by Witek (SM,T)

This can be easily done. However I am not a fan of such metrics. They can be misinterpreted and can cause bad decisions.

The severity for example can change during the lifetime of an issue. It could start as severe. Then a developer creates a quick workaround. The severity then changes to minor. How do you handle such situations? Do you close the severe issue and create a new one for the final fix?

Thu, Jan 3, 2013, 15:42 by Aruna Gutta

Yes, I would close the severe issue with workaround and create minor issue.


Post a comment