Repository navigation
Maintaining a project board to manage feature requests #41988
Description
Refs: #41113
I started experimenting with it in Node.js feature requests
I think that if done well it will be beneficial for us collaborators and for users.
Now if other people agree with me, the next steps would be:
- Determine the fields (and their possible values) that we need to filter and organize the issues efficiently.
- Determine the views that we want to make available.
- Add all existing open feature requests to the project.
- Setup a GitHub action that adds an issue to the project when it is labeled "feature request" and removes it from it when the label is removed.
- Update the feature-request-management document
/cc @nodejs/tsc
Activity
mcollina commentedon Feb 15, 2022
go ahead, I like the proposal!
mmarchini commentedon Feb 16, 2022
It's been a while since I've used GH projects, but I think we can automatically assign issues with feature request label to the project without a GitHub action. Also +1 this seems like a good way to organize things
targos commentedon Feb 16, 2022
Automated workflows for GH projects are quite limited right now. I don't see anything related to labels: Node.js feature requests
mhdawson commentedon Feb 16, 2022
+1 to the suggestion from me.
In terms of:
A few thoughts to kick off the discussion:
never staletargos commentedon Feb 20, 2022
I like that idea. I don't know if we can filter using the creation date, though.
Not sure we can do that out of the box.
Maybe we could do an action (cron) that maintains a label on these issues.
SGTM. I added the view, but there is no issue with this label at the moment.
targos commentedon Feb 20, 2022
About the "Status" field, here are the values I put for now:
Did I miss anything?
targos commentedon Feb 20, 2022
With the future stale bot closing feature requests after a period of inactivity, we probably need a status for those, because they are not necessarily something that we don't want in core.
mhdawson commentedon Feb 21, 2022
@targos I think they would have the tag
staleon them, but we can confirm after I get the closing working.targos commentedon Feb 23, 2022
I added a "Stale" status for those.
github-actions commentedon Jun 25, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon Jul 26, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.