Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-44305

Messages > Compose Message > Specify Recipient > Save Draft > Recipient not Saved

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Verified
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 11.4, 12.0, 19.6, 20.2, 21.0, 22.0 [Tentative]
    • Fix Version/s: 21.0, 22.0 [Tentative]
    • Component/s: Messages Tool
    • Labels:
      None
    • 21 Status:
      Verified
    • 20 status:
      Won't Merge
    • 19 status:
      Won't Merge
    • Conversion Script Required:
      Yes
    • Test Plan:
      Hide

      In Trunk, navigate to a course site that contains some student recipients and the Messages tool.

      1. Click the "Messages" tool.
      2. Click "Compose Message."
      3. In the "To" field, specify the recipient "All participants."
      4. Check the CC box
      5. Fill out any other fields and message body as necessary. (Note: the subject and body are required fields). 
      6. When finished, click "Save Draft."
      7. Now, click on the "Draft" folder in Messages.
      8. Click on the "Subject" link to view the draft.
      9. Note that the previously specified recipient is now missing. The instructor would need to specify this once again before sending it. 

      If this has been fixed, then upon saving a draft with a specified recipient, the user would see the saved recipient in the draft upon returning and the CC box would be checked.

      Repeat the above with groups and roles as selections, both in CC and BCC fields. Repeat again, this time deleting a group before reopening the draft.

      Repeat again as a student who can only send messages to their group members (has only "Allow send to own group..." permissions).

       

      Show
      In Trunk, navigate to a course site that contains some student recipients and the Messages tool. Click the "Messages" tool. Click "Compose Message." In the "To" field, specify the recipient "All participants." Check the CC box Fill out any other fields and message body as necessary. (Note: the subject and body are required fields).  When finished, click " Save Draft ." Now, click on the "Draft" folder in Messages. Click on the "Subject" link to view the draft. Note that the previously specified recipient is now missing. The instructor would need to specify this once again before sending it.  If this has been fixed, then upon saving a draft with a specified recipient, the user would see the saved recipient in the draft upon returning and the CC box would be checked. Repeat the above with groups and roles as selections, both in CC and BCC fields. Repeat again, this time deleting a group before reopening the draft. Repeat again as a student who can only send messages to their group members (has only "Allow send to own group..." permissions).  

      Description

      The Messages tool is a lot like an email inbox in a course site. As such, it can be very handy to instructors and students, especially if students/instructors need another way to communicate with each other, other than by email or phone. 

      If a user begins to compose a message, specifies the recipient, and all other fields as necessary, and then saves the draft, upon returning to that draft later on, the user will find that the recipient is no longer listed. 

      This is a bit unlike the email experience, where saved email drafts DO, in fact, save the recipient in the "to" field. In addition, instructors may very well have a desire to draft a message to all student participants, and return later to send it, only to find that they must specify the recipient of "all participants" once again just to send it.

        Gliffy Diagrams

          Zeplin

            Attachments

              Issue Links

                Activity

                  People

                  Assignee:
                  plukasew Paul Lukasewych
                  Reporter:
                  jbuckin2 John C Buckingham
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  9 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration