search

dotnet / fabricbot-config

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

Archived issues are not resurrected into Needs Triage column #4

Closed jeffhandley closed 2 years ago

jeffhandley commented 2 years ago

After we archive issues on the triage boards, if further activity occurs from the community, the issues are not getting resurrected back into the Needs Triage column as expected.

The task is firing as expected, but it's taking the action of simply adding the issue to the project column, which fails silently if the issue is already on the board in a different column, but archived. To work around that, issues need to be removed from the board and then re-added to the board into the Needs Triage column.

This has the down-side of causing extra noise in the issue events when a issue is moved from Triaged to Needs Triage, as 2 events (remove/add) are shown instead of 1 (moved to column). There aren't any known mechanisms for un-archiving a card or detecting if the card is archived, but those capabilities could also be researched further.

jeffhandley commented 2 years ago

This is blocking us from archiving issues during the monthly pod syncs, as some pods are relying on the resurrection to give them the indicators they need to re-review issues.

jeffhandley commented 2 years ago

This fix will be included in the next updates to each of the repositories.