Skip to content

Draft communication with no recipients does not appear in communication history #6979

Description

@austinspooner

Description

A simple communication saved as a draft with no recipients does not appear anywhere in the communication listing blocks. The Communication record is created successfully and loads correctly when accessed by direct URL, so the record exists and is in Draft status. It just has no discoverable path back to it through the UI.

The practical effect is that the draft is created and then lost. Unless the user happens to have the communication ID or a saved link, there is no way to return to it, resume editing, or add recipients. This was found using the new AI feature in v19.4 when we asked it to create a draft communication and could not see the communication. When we asked for the direct link using the communication ID we were able to get to the draft communication.

Actual Behavior

The draft is absent from the listing blocks. No error or warning is shown at save time, so there is no indication to the user that the communication they just saved has become unreachable.

https://app.screencast.com/g8XwUJ2YEVNlf

Expected Behavior

A recipientless draft should still be reachable. At minimum it should appear in the Communication List History block so the author can find it and finish it.

Steps to Reproduce

Start a new communication using the simple communication editor.
Enter a subject and body but do not add any recipients.
Save the communication as a draft.
Look for the draft in the Communication History block and in the Communication List block.
Observe that it does not appear in either.

Issue Confirmation

  • Perform a search on the Github Issues to see if your bug is already reported.
  • Reproduced the problem on a fresh install or on the demo site.

Rock Version

v19.4

Client Culture Setting

en-US

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions