Brainstorming redux

[jennifer]

I've read through the comments to the brainstorming post and these are the most popular requests I'm seeing:

- ability to preview and/or edit screened responses
- adjustment of point assignments
- approval links on a given answer instead of having to use the drop-down
- better tracking of when a request was last touched and in what way (screened answers, ICs)
- responding directly to other responses (threaded comments)
- improved filtering/sorting/tagging
- view of all requests a given user has sent in
- view of all requests a given user has answered
- per-request notifications
- better wording for support email notifications
- linking of support requests to Zilla bugs with access to relevant stats
- ability to reference multiple FAQs

That sounds like a pretty heavy overhaul, but I think if we work on a chunk at a time, it'll get done!

If there's no objection I can open a Bugzilla item for each of the bullet points I've listed above. Any additional discussion about implementation details can go in comments to this post for now.

Comments

[aveleh]

view of all requests a given user has sent in

Unless I'm misunderstanding, the above already exists, it's just only available to SHs and relies somewhat on username/email combinations.

http://www.dreamwidth.org/support/history.bml?user=
http://www.dreamwidth.org/support/history.bml?email=
etc, etc.

One advantage of an actual overhaul could be to better organize tools associated with priv packages.

[jennifer]

Now that I look, I see the email address displayed on a support request is a link to history.bml. I had assumed it was a mailto.

The request was for a user to be able to see a list of their own requests, not just the support crew.

[wyntarvox]

it's just only available to SHs

Yeah, one of my suggestions was to make it more widely available, or just remove the priv requirement. At least for the username version. Email version should probably stay where it is (which I think is finduser or supportclose?), since people obviously have different privacy settings for their email address.

[pauamma]

Why shouldn't it follow the user's email display setting? Or maybe only a subset, eg "if public, display and allow search for everyone - if not public, limit to people with suitable privs" {the restriction being in case Alice trusts Bob to see her email address, but not Carol - if Bob doesn't know that, and esp. if he's used to the way LJ does things, he may let it slip)