Page MenuHomePhorge

Configure another Ponder Question status "Closed, Graduated"
Open, Needs TriagePublic

Description

We ask people to file bugs via ponder, and then create tickets out of them, but there's no good status for what happens next - we can close the question as "Resolved", "Obsolete" or "Invalid", none of which are correct.

Hopefully, there's a configuration for that...

Event Timeline

I sincerely thought that "Obsolete" was the good one semantically.

I agree that an additional status is needed for closing when creating a task. Current statuses are not obvious. "Closed, Graduated" is good to fast decision.

I agree that an additional status is needed for closing when creating a task. Current statuses are not obvious

@Iniquity is there anything against the already-existing "Obsolete" in your opinion? (Sincere question. I'm not native English and it sounded good to me)

To me, "obsolete" manes "no longer appliable" - basically, "the information in this page doesn't apply any more".
Some (made up) examples:

  • "Can Phorge run on PHP 7.0?" (The answer is no, because of a specific bug in 7.0, which was EOL a long time ago)
  • "I have this problem in the Chatbot app" (We've deleted the chatbot app)

"Graduated" fits better for "this is a valid question/request, but the answer is too complex to fit in a Ponder page".

"Resolved" fits questions that got a simple answer, and "Invalid" is for things where the question turns out to be completely broken (e.g., a user error in something that's not part of system).

Basically, if someone is searching for information to solve a real issue, they would normally skip anything marked Obsolete.