Discussion thread on #8200

[ssbarnea]

I can understand why you wanted to take the feature request out of the issue tracker as I faced this problem with other projects too.

While I do not have a definitive answer for myself, I cam make few notes here based on what I tried:

• Issue being closed can misled users. Luckily there are two possible alternatives:
  • Convert feature request into a special discussion. Keep all history and comments and automatically redirects. Bad part is that they cannot really be used planning.
  • Move the feature request to another backlog repository as this allows discussions and planning. Downside is that they would reside on another project inside the organization, so finding existing feature requests.. would not be very easy.
• Locking the issue and suggesting to use discussions is ok, but the link to discussions was not to a newly created thread, so anyone that would one would not be able to see existing ones. That is not very friendly. Easy to fix by reporting the generic link to thread like this one

[squidfunk]

Thanks for your feedback!

Convert feature request into a special discussion. Keep all history and comments and automatically redirects. Bad part is that they cannot really be used planning.

We have considered this approach, but since we cannot add it to the project board, it's not feasible. Also, we would need to convert the discussion back to an issue, leading to more noise, and I don't think subscriptions are carried over. The fact that users can still subscribe to updates, although the issue is closed, is better than needing to jump through more hoops. Thus, keeping it as an issue, is the best compromise we could find. Ideally, GitHub would have a "Closed for later consideration" state for issues.

Move the feature request to another backlog repository as this allows discussions and planning. Downside is that they would reside on another project inside the organization, so finding existing feature requests.. would not be very easy.

This is an interesting idea. However, issues would also be moved around, unsure if the subscriptions are carried over, and as you mentioned, discoverability is not ideal. We'll keep experimenting ☺️

Locking the issue and suggesting to use discussions is ok, but the link to discussions was not to a newly created thread, so anyone that would one would not be able to see existing ones. That is not very friendly. Easy to fix by reporting the generic link to thread like this one

We're gradually adapting the feedback that we receive, and we do not intend to create a large consolidated discussion on this topic, which is why we did not create one. The announcement was intended to be an FYI, which is why I locked it. I understand that this might be controversial, but that's how it is with large Open Source projects. If we feel that there's really something to discuss (besides the super useful feedback that we receive), we'll open one ☺️