Issues Service

[andrew]

Collect and generate statistics for issues and pull requests

Interesting stats include:

• average time to close issues
• average time to close pull requests
• number of unique issue creators
• number of unique pull request creators
• average number of comments on an issue
• average number of comments on an pull request
• label breakdowns
• stats over certain date ranges
• bot activity

Upvote & Fund

• We're using Polar.sh so you can upvote and help fund this issue.
• We receive the funding once the issue is completed & confirmed by you.
• Thank you in advance for helping prioritize & fund our backlog.

[Ly0n]

I find it helpful to see if a project creates commits in conjunction with closing issues. This shows that the project has a development process that enables multiple developers.

[andrew]

There's a handy table of events we can get for github issues and pull requests in the two apis they have access to here: https://gist.github.com/dahlbyk/229f6ee762e2b0b45f3add7c2459e64a

[Ly0n]

As a quality indicator, I have looked for issues from external developers/users for my research. It proves to a certain level that a software can be used / installed from a third party. Maybe this is also interesting for others: Number of Issues from external users

[andrew]

Work is happening over here: https://github.com/ecosyste-ms/issues

[andrew]

@Ly0n here's how it's looking so far, will be deploying it soon:

[andrew]

The service is now online, still a little bit of setup to do but mostly ready: https://issues.ecosyste.ms/hosts/GitHub/repositories/octobox%2Foctobox

[Ly0n]

The "Issue Author Associations" are perfect for our study. @joshhopkins

[joshhopkins]

Indeed @Ly0n . Great stuff @andrew.