Some issues, specifically on diagnosis and needscontact stage stays for a long time on this stage.
Sometimes, someone started a diagnosis, but the issue stays in this state for a long time. Some cases:
diagnosis has been started by someone and there is an intent to go back to it.
we come back to it in a reasonable time
we forget it because GitHub UI is not that good for reminding old issues.
diagnosis has been started by someone and there is a blocker, which prevents the person to finish.
ping someone else to finish it or ask help
leave it as-is
On GitHub there is a notion of assigned for an issue, maybe we can leverage this with two states:
Assigned: Person X is working on it
Not assigned: Free to take (before and during diagnosis).
It means we could advertise to the rest of the community that
someone is working on it in the UI.
grab this information to display in the activity page (tool to help people assigned to remember what they are working on.)
Usernames of people to assign this issue to. NOTE: Only users with push access can add assignees to an issue. Assignees are silently ignored otherwise.
Some issues, specifically on diagnosis and needscontact stage stays for a long time on this stage. Sometimes, someone started a diagnosis, but the issue stays in this state for a long time. Some cases:
On GitHub there is a notion of assigned for an issue, maybe we can leverage this with two states:
It means we could advertise to the rest of the community that