Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status field on support history page less useful than it might be #1402

Closed
rahaeli opened this issue May 30, 2015 · 3 comments · Fixed by #1454
Closed

Status field on support history page less useful than it might be #1402

rahaeli opened this issue May 30, 2015 · 3 comments · Fixed by #1454

Comments

@rahaeli
Copy link
Contributor

rahaeli commented May 30, 2015

The 'status' column on http://www.dreamwidth.org/support/history only distinguishes between 'open' and 'closed'. This is not very useful! It should use the same as the support board itself: 'open', 'answered, awaiting close', 'answered, still needs help', and 'closed'.

@kaberett
Copy link
Contributor

claimed!

@kaberett
Copy link
Contributor

Okay, so support/history pulls directly from the database table support, for which the "status" property only offers "open" or "closed" (http://wiki.dreamwidth.net/wiki/index.php/Database_Table:_support). support/help looks to be doing a closer approximation to working out subtype of "open" status on the fly. Consequently the best way I'm seeing of handling this at the moment is if, for support/history, the database status field is set to "open", do the same set of checks as are done over in support/help and display the appropriate subtype. I'm going to go ahead with trying to implement that for the time being but appreciate input!

@rahaeli
Copy link
Contributor Author

rahaeli commented Jun 1, 2015

Of course it's not that easy, heh.

I haven't looked at the actual code, but your proposed method is probably the best, as long as you refactor it so both areas are calling out to the same code as a subroutine instead of duplicating the checks in both places. (I might be overruled, though!)

me-and added a commit to me-and/dw-free that referenced this issue Jun 27, 2015
Rather than just listing "open" or "closed" alongside each support
ticket, work out and also list as appropriate "additional help needed"
or "awaiting close".

Fixes dreamwidth#1402.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants