How to measure perfomance of issue solving

Hello GitLab community! I am looking for ideas and best practices on how to effectively measure my teams’ performance using GitLab Issues. Currently, I am using the ISSUES resource to track bugs reported by end-users, and both my development team and product team are utilizing this feature. I have implemented a labeling system to monitor the progress of each issue, but I am now interested in measuring the time spent on different statuses. I would greatly appreciate your insights and suggestions on how to accomplish this effectively.

Description of the Current Setup: To provide some context, my team uses GitLab Issues to manage the development of issue solutions. We have defined the following labels to represent various stages in the issue resolution process:

  1. Status: Open
  2. Status: Product Analysis
  3. Status: Development Analysis
  4. Status: Development Acting
  5. Status: Done

These labels help us track the progress of each issue and provide a clear picture of its current status. However, we would like to go a step further and measure the time spent on each status to gain insights into our team’s efficiency and identify areas for improvement.

The primary goal of this discussion is to gather ideas and recommendations from the GitLab community on how to measure the duration an issue spends in each status, broken down by the assignee. By analyzing this data, we aim to gain valuable insights into the performance of our teams and individual contributors, allowing us to optimize our processes and enhance productivity.

To kick-start the conversation, I would like to propose the following questions:

  1. What are the recommended approaches or tools to measure the time spent on each status for GitLab Issues?
  2. Are there any existing GitLab features, plugins, or integrations that can provide this type of performance measurement out-of-the-box?
  3. How can I extract the relevant data from GitLab to calculate the duration an issue stays in each status?
  4. What are some best practices for interpreting and visualizing the collected data to gain meaningful insights?
  5. Are there any potential challenges or limitations to consider when implementing this measurement system?
  6. Is working with these labels the best way to keep track of the status of each issue? Or are there better approachs?

Please feel free to share your experiences, suggestions, and any relevant resources or examples that can help us effectively measure our teams’ performance using GitLab Issues.

Thanks in advance.