Skip to content
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.

Give repo owners the ability to "Approve" an answer to an Issue (just like on StackOverflow) #664

Open
brock opened this issue May 2, 2016 · 5 comments

Comments

@brock
Copy link

brock commented May 2, 2016

  • Issue opens with a question
  • Below the question is a "promoted" answer that is designated as the Approved Solution
  • The original ordering of all responses should stay in tact, so that everyone can see where and when the Approved Solution originally appeared.
  • Consider making the "Approved Solution" a simple link, with the same text across all repositories. IE: you don't actually duplicate the solution in a box below the question, you simply link to the Approved Solution. It might look like this:
    • "There is a response to this issue that has been marked as a Solution."

You could even go crazy and give both the repo owner and the person asking the Issue permission to mark it as approved. Like this:

  • "There is a response to this issue that has been marked as a Solution."
@brock
Copy link
Author

brock commented May 2, 2016

Inspiration for this idea was birthed here. In this example, the issue was opened in September of 2014. It was closed then re-opened. It is now closed. As of today (May 2016) there is still activity as recent as 8 hours ago.

Think how much time is lost scrubbing through this issue when an answer might be known by both parties.

@jwerre
Copy link

jwerre commented May 3, 2016

+1

@cirosantilli
Copy link
Collaborator

@jwerre please use the new +1 button feature instead of comments to avoid notifying people and have an automated upvote count ;-)

@cirosantilli
Copy link
Collaborator

Would also help: #601

@Prinzhorn
Copy link

This is such an essential and basic feature. How often do you browse a closed issue (for example a feature request) and have to skim through 154 comments to find out:

  1. if is has been implemented or not
  2. In which release
  3. What the API looks like

I have to do this all the time. Instead of just marking a comment as the solution I propose that closing an issue also prompts for an optional summary/reason, which is then displayed at the top. It could answer all the questions above and also summarize the process that lead to it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants