search

dotnet / fabricbot-config

Scripts for managing fabricbot configurations in the dotnet repos
MIT License
4 stars 7 forks source link

Automatically move engaged issues into triage columns #7

Closed jeffhandley closed 2 years ago

jeffhandley commented 2 years ago

When a team member begins engaging on an issue, we could automatically move the issue into their triage column. This is similar to #3.

Some team members have requested that when they comment on an issue, it could be automatically moved into their column on the issue triage project board. When we introduced the issue/PR project boards, we stated that there would be no automation to move issues/PRs into the "middle" columns, but this is a popular enough request that we should consider it.

We could trigger this off of the actions of assigning an issue to a team member while it remains untriaged, or when a team member comments on an issue and it's still in their Needs Triage column.

If we do implement this, we'll need to have something that maps the github username to the pod member's columns on the boards.

jeffhandley commented 2 years ago

More testing is needed on this to ensure comment interactions are counted as engagements

jeffhandley commented 2 years ago

This should be working now

jeffhandley commented 2 years ago

Fixed by #16

jeffhandley commented 2 years ago

There are some remaining issues with this and #3 because of essentially having race conditions for adding items to the board into targeted columns. Reopening for a different approach to be taken.