Issue Reaction Time

This check queries the GitLab API for the minimum time it takes for a project member to react to an issue in the given time range. The check passes if the number of commits is greater than or equal to the minimum threshold.

- type: ISSUE_REACTION_TIME
  description: "Describe the check in context of your badge and level"
  threshold:
    timeRangeInMonths: 3
    max: 7

The issue response time is the time between the creation of an issue in a project and the first valid response.

A project member is a user matching one of the following criteria:

• A member of the project (as returned by the project member API of GitLab)
• A user who has created at least 5% (magic number) of all issues and/or commits in the project

The conditions apply simultaneously and not independently of each other:

• If a project does not have any issues, the check will pass.
• Issues created by project members are not considered.
• Every (automatic) action in the stream of an issue, except comments such as “Mentioned in MR” or “labeled” or “Assigned to” etc. are evaluated as a valid issue reaction.
• A comment is considered a valid response if the comment is submitted by a project member.
• A comment is not considered a valid response if a non-project member responds to the ticket of a non-project member.

Background

Measuring issue reaction time is a valuable metric for assessing a project’s maintenance and responsiveness. A quick reaction time indicates that project maintainers are actively monitoring and addressing issues, which reflects good project health and responsiveness.

• Indicator of Active Maintenance: Fast issue responses signal that the project is being actively maintained, with attention to bugs, feature requests, or other user concerns. Slow reactions might suggest neglect, which could impact the user experience or drive away contributors.

• Community Engagement: Quick reactions from project members also demonstrate an engaged and supportive community. It shows that maintainers or contributors are available to help, fostering a more collaborative and productive environment.

• User Confidence: Projects with shorter issue reaction times inspire greater confidence in users, as they know their concerns will be addressed promptly, making the project more appealing for adoption and contribution.

In summary, tracking issue reaction time helps gauge the level of active maintenance, community involvement, and responsiveness, which are crucial for the long-term success and sustainability of a project.