Count the number of times a feature or requirement goes into a status

What is the challenge?

For development cycles (Aha Develop), it's important to know how many times a feature is returned to development as a means to determine if a developer is doing proper unit testing or adhering to acceptance criteria.

What is the impact?

Identifying features/requirements that have been returned frequently can help identify a training need or performance improvement opportunity. The product manager/owner may need to write better acceptance criteria, or the developer may need to take more care in terms of testing their work prior to sending to QA. This has applicability beyond development as well.

Describe your idea

Allow for the system to count the number of times a record has entered a specific status and then allow that measure to be reportable.