View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
5800 | Composr | General / Uncategorised | public | 2024-07-23 02:33 | 2025-02-02 00:22 |
Reporter | PDStig | Assigned To | PDStig | ||
Priority | normal | Severity | feature | ||
Status | resolved | Resolution | fixed | ||
Summary | 5800: Enhance the warnings tab with useful info about active punitive actions | ||||
Description | Make the warnings tab on user profiles more helpful by communicating not just warnings history but also active punitive actions and account standing. * Rename tab to "Standing", and make it always visible to each member and high-level staff * Add a stepper at the top with indications for various categories of standing / punitive actions (e.g. "Warnings" for when a formal warning exists on the account, "Restrictions" for when the member's privileges or permissions are restricted [e.g. silences], and "Probation" for when the member is in probation.) * Under the stepper, clearly communicate each active restriction or punitive action in effect, to what it applies, and how long until it expires (or when it expires). Use an icon "bullet" on each item. * Finally, list the warnings history under that. This should operate via the cns_warnings hooks; add a new function which defines what each hook will render on this tab. This includes the name of the stepper item (if adding one) and whether or not it is active, and a list of items to put under there (e.g. active punitive actions). - Note for steppers, multiple hooks can define a stepper with the same name. In that case, only one stepper with that name is added, and if any one of the hooks specified to have it active, it will render as active. The highest order (farthest left) defined will be used. - Stepper order should also be defined for each hook specifying a stepper item. | ||||
Additional Information | See https://compo.sr/forum/topicview/browse/developing/composr-v11/v11-experiment-with-the.htm?post_id=9981&redirected=1#post_9981 For an example design. I might end up doing this myself as I've already implemented something similar on another site (though it doesn't use the hooks ATM). | ||||
Tags | Roadmap: Over the horizon | ||||
Attach Tags | |||||
Time estimation (hours) | |||||
Sponsorship open | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2024-07-23 02:33 | PDStig | New Issue | |
2024-07-23 02:33 | PDStig | Tag Attached: Roadmap: Over the horizon | |
2024-07-23 02:34 | PDStig | Description Updated | |
2025-02-02 00:22 | PDStig | Assigned To | => user4172 |
2025-02-02 00:22 | PDStig | Status | Not Assigned => Resolved |
2025-02-02 00:22 | PDStig | Resolution | open => fixed |