#220 Customize Messages view in the Admin interface
Closed: complete by jflory7. Opened by anasustic.

Summary

Customize Messages view in admin.py for the Admin interface.

Background

Messages appear as a list of individual records, indentified by the string created with the Message's model __str__() method which is the identifier, and linked to detailed views/forms for editing. Fields in the detailed Messages view/form appear listed in the same order as defined in the model.

Details

For the Messages list view, we could display the sender_name, receipient_name, status and identifier.
For the Messages list filter we could include status and maybe sender_approved_public and receipient_approved_public fields.
For the Messages detailed view we could organize the fields in sections for:
- Sender,
- Receiver,
- Message,
- Status and the identifier,
and maybe organize some Boolean fields (ie. Sender named, Sender approved public, Sender approved public named, ...) horizontally.

Outcome

This would make it easier to approve new Messages.


Metadata Update from @jflory7:
- Issue priority set to: waiting on assignee (was: awaiting triage)
- Issue tagged with: PASSED, difficulty - medium, good first issue, help wanted, improvement, type - frontend

Metadata Update from @jflory7:
- Custom field Requirement # adjusted to 10

Metadata Update from @shraddhaag:
- Issue assigned to shraddhaag

I have filed PR #240 addressing this issue. @jflory7 Please let me know if the categorisation makes sense or if I need to modify it.

Super work on this one @shraddhaag! :raised_hands: Closing as complete.

I wanted to show off the difference and how easier it is to read the admin portal from your PR:

All messages view

Before:

Screenshot of admin Messages view with message ID string as only value shown

After:

Screenshot of admin Messages view with multiple pieces of information shown

Specific messages view

Before:

Screenshot of editing a specific message without categories

After:

Screenshot of editing a specific message with categories

Metadata Update from @jflory7:
- Issue close_status updated to: complete
- Issue status updated to: Closed (was: Open)

Metadata Update from @jflory7:
- Issue set to the milestone: Summer Coding 2019: phase 1

Metadata Update from @jflory7:
- Custom field Requirement # reset (from 10)