Streamline status reporting in Secure's static and dynamic analysis groups
We spend an inordinate amount of time reporting status as part of our normal cadence.
- Weekly during 1:1s.
- Ad hoc basis in slack or in the issue(s) themselves when they become escalated or wrapped up in other investigations.
- As part of release planning, trying to determine what might slip.
As an engineering manager, product manager, stakeholder, product owner, or other interested party, I'd really like an easy way to discern the status of any one issue without having to ask for an update. We have workflow labels, but these labels are mutually exclusive and only allow an issue to be in zero or one state at a time. The team has noted it's not uncommon for issues to be in two or more states simultaneously, depending upon the number of MRs required to deliver some issues.
Are there methods by which we can adopt to make status reporting more automated without significantly upping the burden upon the DRI assigned to it?
Edited by Thomas Woodham