...

1. Appearance / availability / functionality of post actions and labels based on user role
   1. reporting (flagging) - always available to all users
      1. Students' reported status should only indicate whether or not they individually reported the post
      2. TAs / Mods / Admins see the reported status when any user has reported the post
      3. When TAs / Mods / Admins un-report reported posts, the changed status should take effect for all users
   2. voting - always available to all user types on threads and responses (not comments)
   3. pinning - only changeable by TAs / Mods / Admins
   4. closing - only changeable by TAs / Mods / Admins
   5. endorsing - only for discussion responses - only changeable by TAs / Mods / Admins
   6. marking as answer - only for question responses - only changeable by thread author and TAs / Mods / Admins
   7. following - available to all user types at thread level only
   8. editing and deleting - always available to TAs / Mods / Admins or the content author
2. Correct behavior for Discussion threads vs Question threads
   1. endorsement rules differ for authors - they can only endorse (mark answers) on question threads
   2. responses marked as question answers are always clearly designated as such (appear in a separate section, include answer marker and date info)
   3. answered and unanswered questions are always clearly distinguished from discussion threads in the sidebar
3. New sidebar thread list filters 
   1. Flagged thread filter is only available to TAs / Mods / Admins
   2. Unread thread filter accurately filters unread threads for the presently active user
   3. Filters correctly interact with category selection (discussion categories, "posts i'm following" filter)
   4. searches
4. Tabs vs. inline: thread display should look and behave the same in both tab and inline mode
5. AJAX - post actions (voting, pinning, following, reporting, closing) should be exercised to ensure they continue to function correctly.
   1. Errors can be deliberately triggered by killing the comments service and/or the LMS
6. Closed threads: we should ensure we haven't regressed behavior with regard to closed threads.
   1. example: on recent inspection of our branch the "add a comment" box currently appears on closed threads, which may or may not be a regression.

Sandbox Info

http://forums.m.sandbox.edx.org/

in addition to the standard provisioned user accounts, there's a few extra set up for convenience

• jsa+ta@edx.org / edx   (a community TA enrolled in edx 101)
• jsa+moderator@edx.org / edx   (a moderator enrolled in edx 101)
• also, staff@example.com has been granted the discussion admin role in edx 101

Code Version

https://github.com/edx/edx-platform/tree/gprice/forum-action-cleanup   / commit: afd9aa35e4dffe391b6915d386fe5a5fe46174f5

We have deployed this sandbox from the tip of a working branch because we have a few more minor changes to make but we don't want to block testing from starting.

In general, here is what we can expect to change in a subsequent update:

• a handful of accessibility-related adjustments (making new controls available via keyboard / screen reader) - not expected to change present appearance or mouse interactions
• a bunch of javascript test fixes (which should be entirely invisible)
• a merge / rebase of this branch (not expected to impact functionality at all)

We will keep this section updated depending on any discussed / agreed-upon plans to redeploy.