Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Communication Still Sends Even When Backdated #1999

Closed
nathanp opened this issue Jan 31, 2017 · 1 comment
Closed

Communication Still Sends Even When Backdated #1999

nathanp opened this issue Jan 31, 2017 · 1 comment
Labels
Status: Available The core team has made this available for the community to fix. (was: Status: Available) Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. x-Fixed in v6.4
Milestone
v6

Comments

@nathanp
Copy link

nathanp commented Jan 31, 2017 •
edited by sparkdevnetwork-service

Description

When scheduling a communication, if a user accidentally selects a previous date instead of a future date, the communication immediately sends. It would be helpful instead if the communication did not send and there was some type of notification to the user to please select a future date/time in order to properly schedule the message.

  • Rock Version: [6.1]
@JimMichael
Copy link
Collaborator

I would also add a similar issue... if you leave the date blank and just enter a future time, it sends immediately. Since the UI doesn't force you to enter a date, it's possible someone assumes just entering a time (with no date) means "today", which is not the case.

@jonedmiston jonedmiston added the Status: Available The core team has made this available for the community to fix. (was: Status: Available) label Mar 24, 2017
@JimMichael JimMichael added the Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. label Mar 24, 2017
@shivambareria shivambareria mentioned this issue May 1, 2017
Merged
azturner added a commit that referenced this issue May 5, 2017
@azturner
+ Updated the Communication Entry block to validate the future send d…
f62b229 
…ate/time (Fixes #1999)

- Fixed whitespace
@crayzd92 crayzd92 added this to the v6 milestone Mar 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: Available The core team has made this available for the community to fix. (was: Status: Available) Status: Confirmed It's clear what the subject of the issue is about, and what the resolution should be. x-Fixed in v6.4
Projects
None yet
Milestone
v6
Development

No branches or pull requests
5 participants
@jonedmiston @azturner @nathanp @JimMichael @crayzd92