Skip to content

chore: Remove the feature request issue template#3622

Merged
EmandM merged 5 commits intodevelop-2.0.0from
chore/remove_feature_requests
Mar 17, 2026
Merged

chore: Remove the feature request issue template#3622
EmandM merged 5 commits intodevelop-2.0.0from
chore/remove_feature_requests

Conversation

@EmandM
Copy link
Member

@EmandM EmandM commented Aug 25, 2025

Purpose of this PR

Removing the Feature Request issue template from this repository as feature requests should probably go through the discussions board.

Jira ticket

n/a

Changelog

Simply an infra PR, doesn't include any package changes.

Documentation

  • No documentation changes or additions were necessary.

Testing & QA

No testing required

Functional Testing

Manual testing :

  • Manual testing done

Automated tests:

  • Covered by existing automated tests
  • Covered by new automated tests

Does the change require QA team to:

  • Review automated tests?
  • Execute manual tests?

If any boxes above are checked, please add QA as a PR reviewer.

Backports

Backported by #3623.

@michalChrobot
Copy link
Member

I'm not sure if we didn't have this discussion at some point and decided that Feature requests are ok to have in the repo (but maybe @NoelStephensUnity can correct me). There are some ups and downs since some feature requests should be definetly in discussions but for some users can be really helpful with some initial code changes suggestions (but that's my perspective, I might be wrong)

@NoelStephensUnity
Copy link
Member

I'm not sure if we didn't have this discussion at some point and decided that Feature requests are ok to have in the repo (but maybe @NoelStephensUnity can correct me). There are some ups and downs since some feature requests should be definetly in discussions but for some users can be really helpful with some initial code changes suggestions (but that's my perspective, I might be wrong)

I am in this same mindset. It should be "ok" for a user to provide a feature request via GitHub (since the majority of feature requests are actually done in GitHub anyway).

@michalChrobot
Copy link
Member

I think Emma has some good arguments of

  • If you look at the open issues with type:feature on them, only one is from this year.
  • There may be a point that the tag was useful when NGO was under active development and growth, but doesn’t fit our current workflow with the project.
  • We have an option already for “Feedback” that points to the discussions board.

Some feature requests can be usually resolved by pointing the correct solution/workaround and if something would be interesting then we could import it to Jira as a task. Another option for users would be to create PRs in the repo so we can better understand what they want to do (based on changes and PR description)

@NoelStephensUnity what you think? With those arguments I think I would be ok with removing it/pointing to discussions

@cla-assistant-unity
Copy link

cla-assistant-unity bot commented Dec 2, 2025

CLA assistant check
All committers have signed the CLA.

Copy link
Member

@michalChrobot michalChrobot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on the current NGO planes I'm quite ok with following on your thoughts from back then so I think we can just merge this removal

@EmandM EmandM enabled auto-merge (squash) March 17, 2026 17:22
@EmandM EmandM merged commit 7c515b3 into develop-2.0.0 Mar 17, 2026
11 checks passed
@EmandM EmandM deleted the chore/remove_feature_requests branch March 17, 2026 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants