-
Notifications
You must be signed in to change notification settings - Fork 7
Insights
Ideas for what insights we would like elasticboard to provide.
Find out why this happened:
- maybe the issue was estimated for a different skill level
- maybe the assignee had to shift their attention to a more important, outstanding issue
Bonus - try to find patterns among overdue issues (i.e. maybe they are all related to a particular component).
How long did it take from the time a person joined the main repo until their first commit/deploy.
Suggest repos (from the org or from the opensource community) that might be a good fit for a person's skill set (computed from past activity).
If someone is assigned to an issue and they haven't touched it in, say, 2 weeks, something must be going on. Maybe they forgot about this issue.
Also worth correlating the amount of "forgotten about" issues relative to their priority labels (i.e. how many critical issues did we forget about?).
Maybe someone reviewed your code and you forgot about that pull request.
It's hard to find older issues, you have to find the exact set of keywords, otherwise you are looking for a needle in a haystack. Issues should be better structured (use [more] labels, for example). We could also provide a way to search through both issues and their comments.
Is a team creating more issues that it's closing/merging? It's interesting for a given period of time to see what the burndown of issues looks like. It might signal an issue cleanup is needed or the team is struggling to accomplish everything that it proposes to accomplish.
How long does it take from the time support opens an issue on github until it gets assigned to someone on the dev team.
Why? To provide visibility into what are we working on right now How? By iterating through the last unique commits of the past working day / week