Proj Mgmt Bot based on Labels

[Harjot1Singh]

No description provided.

[saihaj]

I can do this 😄

[bhajneet]

How I envision the basic project management columns (others can be added outside this for ad hoc purposes):

Step	Column	Reason
1	Triage	New issue, no labels, needs triaging
2	Backlog	Issue is on hold (See label table below)
3	Evaluate	Issue either (1) PM needs developers to explain the significance of issue, (2) needs assignee to estimate for PM to triage further, or (3) assignee needs more info to resolve (bugs that are not confirmed go here) (This should be empty as much as possible)
4	Queue	Issues are ready for assignees to pick up and work on
5	Active	Issues being worked on
6	Review	Issues ready to merge
7	Done	Issues closed, fixed, resolved

---

How I envision labelling (Each issue can have at most ONE status label):

Step	Status	Reason
1	No labels	New issue, needs triaging
2*	Hold	PM doesn't want to evaluate (issue w/ no assignee) or assignee is being held by another issue's resolution (issue w/ assignee)
2*	? ? ?	PM unsure of significance
2*	Score	PM wants estimation details to triage further
2*	Vague	Assignee can't resolve without further details
2*	3hard5me	PM wants it done, but assignee can't resolve
2	To Do	PM wants it done and assignee can resolve
3	WIP	Work is in progress
4	Review / Done*	Issue is linked to PR that will resolve it

• 2* labels can be closed without steps 3 and 4. "To Do" label should go to WIP and then to Review/Done. Basically don't mark something "To Do" unless it's going to be added to Queue in near future
• I would like to combine Review / Done labels as one label called "Status: Merge"

---

Given the above two, I would like the labeller to ease project management:

Label	On Event	Column
None	New	Triage
Status: Hold	Add	Backlog
Status: To Do	Add	Backlog
Status: Score	Add	Evaluate
Status: Score	Remove	(Should be removed by assignee estimating issue) Ping PM to take further action
Status: ? ? ?	Add	Evaluate
Status: Vague	Add	Evaluate
Status: Vague + Type: Fix	14 days stale	Evaluate and ask for more details, warn the issue will self close if labels/info is not provided
Status: Vague + Type: Fix	7 days stale post-warning	Done column, and close issue
Status: WIP	Add	Progress
Status: Merge	Add	Review
Any	Close Issue	Done
Type: Question	Add	Evaluate
Type: Question + Status: Vague	7 days stale post-developer response	Evaluate and ask for more details, warn the issue will self close if labels/info is not provided (be friendly, it could be developer/PM fault for not changing labels after successfully answering)

And then some combos which should automatically go to "Queue" / To Do column (issue requires assignee, if none assigned ping PM for an assignee, as these are ready to go):

Combo1	Combo2	Combo3	Combo4
Status: To Do	Type: Question
Status: To Do	Type: Fix	Impact: High	Diff: 0
Status: To Do	Type: Fix	Impact: High	Diff: 1
Status: To Do	Type: Fix	Impact: Crit	Diff: 0
Status: To Do	Type: Fix	Impact: Crit	Diff: 1

In addition if the labeller sees the comment "Duplicate of #XYZ" it should add the label "Type: Dupe" and close the issue (if it's not already closed). Closing this issue will move it to Done as per above table.

---

Then some helpful queries will become:

• Check Backlog for "To Do" Issues that can be moved to Queue
• List of issues for Harjot to score
• List of issues for Saihaj to score
• List of issues unassigned
• So on and so forth

[bhajneet]

We also don't want to add new labels and remove old labels. We need to be able to modify labels in other repos to new label names so as to not lose all the issues we've tagged.

[saihaj]

We can also label merge if the issue was referenced in a commit. I see in database that there are issues that get commit but the author then makes a big PR and PR is not linked to issue. It will also help in cases if the author forgets to change labels.