Skip to content
This repository has been archived by the owner on Sep 9, 2019. It is now read-only.

Expired message display handling #161

Open
fentie opened this issue Apr 12, 2016 · 3 comments
Open

Expired message display handling #161

fentie opened this issue Apr 12, 2016 · 3 comments

Comments

@fentie
Copy link
Contributor

fentie commented Apr 12, 2016

I was thinking about the concept of messages whose end_date has passed... it makes sense to me to supply some sort of visual affordance to the admins, if not hiding them all together. Perhaps some sort of shading across those records in the index view?

@jessieay
Copy link
Contributor

I could see us having a daily cron job that soft deletes expired scheduled messages. Is that kind of what you were thinking? Agreed that we don't want admins to have to sift through old msgs all the time.

@fentie
Copy link
Contributor Author

fentie commented Apr 12, 2016

It'd depend on how message expiry was used, really... I could see someone wanting to make "seasonal" messages that came up on a recurring basis but were not always active, in which case they would edit the end_date every once in awhile vs. recreating the message each time. Alternatively we could add additional sorting to drop them to the bottom of the list, or add a UI option to toggle showing expired messages or not. There are a lot of patterns out there to choose from.

It might be best to just let the system run with them available for awhile and see how the users employ them?

@jessieay
Copy link
Contributor

@fentie I agree with your "just let the system run with them available for awhile and see how the users employ them?" idea. Will keep this issue open and see if we get any suggestions for hiding expired messages.

Seems like seasonal messages are separate from expired / expiring messages. Another interesting idea although not one I've hard suggested by users yet.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants