Messaging for Mobile Lite Aggregate

Registered by Paul Mark Castillo

MESSAGING FOR MOBILE LIGHT AGGREGATE
Total Estimate: 10 Days

UPDATE: Most of the features are already implemented, except the sending to OrgUnit. Which could be done on the other quarter.

============================================================

FEATURE #1: READING MESSAGES LIST
Estimate: 2 Days

On the Main Menu, there would be a new option called "Messages". Selecting the option "Messages" would go to a new screen called "Messages Screen". The "Messages Screen" contains the inbox, where it would be just a list of Subjects. The unread messages would be marked as a BOLD FONT.

NOTE: On The Web API, you need to look on the individual messages, to know if it is read.

On this screen would have two commands: "Read", "Back".

NOTE: On the WEB API, it doesn't have delete message.
NOTE: On the WEB API, it doesn't have follow up option.

Selecting "Back" would return to the "Main Menu Screen" Selecting "Read" would go to the "Message Screen".

============================================================

FEATURE #2: FILTER MESSAGES LIST
Estimate: 1 Day

On the "Messages Screen" there would be three new filter options: "Show All Inbox", "Show Follow Up Only", and "Show Unread". The options would appear/disappear depending what is the currently used filter. Selecting any of these filters, would update the "Messages Screen".

============================================================

FEATURE #3: READING MESSAGES
Estimate: 2 Days

On the "Message Screen", it contains:
- Label of the Subject
- Label of To
- Messages Thread

The "Messages Thread" would contain:
- Label of the Sender
- Label of Date Sent
- Label of Message

It would contain two options: "Reply", or "Back". Selecting "Back" would go back to the "Messages Screen". Selecting "Reply" would go to the "Reply Message Screen"

NOTE: On the WEB API, it doesn't have mark as unread.

============================================================

FEATURE #4: REPLYING TO A MESSAGE
Estimate: 1 Day

On the "Reply Message Screen", there would be a blank text box, and two options: "Reply", and "Back" Selecting "Back" would go back to the "Message Screen". Selecting "Reply" would send a reply and back to the updated "Message Screen"

============================================================

FEATURE #5: SENDING TO ORG UNIT
Estimate: 2 Days

This is dependent on the Hierarchal Org Unit Selector

============================================================

FEATURE #6: SEND TO INDIVIDUALS
Estimate: 2 Days

On the "Messages Screen", there would be a new option called "Write message". Selecting "Write message", would go to a new screen called "Write Message Screen" The "Write Message Screen" would contain:
- Label of "To user (click to select)" (Selectable)
- Label of Subject
- Label of Text

It would have two options: "Send", "Discard" Selecting the "To user" label, would open/go to the "Select Users Screen", where it would return the selected users to be sent to. Selecting "Discard" would just go back to the "Messages Screen" Selecting "Send" would send the message then go back to the "Messages Screen

Blueprint information

Status:
Complete
Approver:
Peder Andreas Nergaard
Priority:
Medium
Drafter:
Paul Mark Castillo
Direction:
Needs approval
Assignee:
Paul Mark Castillo
Definition:
Approved
Series goal:
Accepted for trunk
Implementation:
Implemented
Milestone target:
milestone icon 2.16
Started by
Paul Mark Castillo
Completed by
Paul Mark Castillo

Related branches

Sprints

Whiteboard

FEATURE #1: Reading Messages List: TODO
FEATURE #2: Filter Messages List: TODO
FEATURE #3: Reading Messages: TODO
FEATURE #4: Replying to a Message: TODO
FEATURE #5: Sending to OrgUnits: TODO
FEATURE #6: Sending to Individuals: TODO

(?)

Work Items

Work items:
FEATURE #1: Reading Messages List: TODO
FEATURE #2: Filter Messages List: TODO
FEATURE #3: Reading Messages: TODO
FEATURE #4: Replying to a Message: TODO
FEATURE #5: Sending to OrgUnits: TODO
FEATURE #6: Sending to Individuals: TODO

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.