-
-
Notifications
You must be signed in to change notification settings - Fork 824
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.
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
Mailings menu: simplify Draft/Sent #24824
Conversation
(Standard links)
|
I also think that the terminology is confusing, and repetitive. A small change but actually super clear and clean. |
Definitely +1. |
@agileware-justin @johntwyman do either of you have any opinions on this? |
@mlutfy here's the regen doco, https://docs.civicrm.org/dev/en/latest/framework/database/#binregensh Probably needs more doco there too and a screenshot. |
@seamuslee001 I agree with any and all changes to improve the UI. |
I definitely like the change to "Draft Mailings". I think that makes a lot of sense. I'm on the fence about the other change. I understand the rationale but would caution that Scheduled is a distinct, meaningful status apart from Sent. |
We could word-replace 'traditional' with 'Olde English' maybe? |
@mlutfy +1 on this. You might want to fix generated data as well. Thanks! |
This is a very valid point, an unscheduled mailing is absolutely still a draft. But a scheduled mailing has not been sent so either the latter link should stay as is or refactor out to three distinct links/views (if possible with just menu/link changes) - Draft, Scheduled (unsent) and Sent |
I agree it's a valid point semantically, but I think (and bear with me), it's where CiviCRM sometimes fails: we try to be very semantically correct, and that means having a very verbose/overloaded interface that makes sense to developers but not to admins. (I don't mean to offend anyone, I'm a dev/geek and have been using CiviCRM for more than 15 years and I haven't bothered to propose to change this until now, I'd often just ducttape around these things.) However, a Scheduled Mailing cannot be edited, so it's not like a Draft. It's really different state (which makes it a valid concern), and the interface makes that clear with different search options. .. but there is a precedent: "in progress" mailings are also a different state, and don't have a special mention in the menu. I'd argue they're probably even more important (when there's a problem). Does it deserve a special mention in the menus? As an admin, what's the difference between scheduled and sent? What's the primary intention when I click on that? If there is no obvious answer, I prefer to keep it simple. During an initial training, very few people ask "where will my scheduled mailings be?". And once they will have sent their first mailing, it will (usually) be intuitive to them because they are redirected to the scheduled/sent mailings page. Personally I would just have "Mailings > Dashboard", which would have a New button, and search options for draft/scheduled/sent, but I'm not into drastic changes, so I'm trying to do small iterative changes that most people won't notice (similar to #23831, no complaints so far). |
Fair enough |
Keep in mind that with Drupal there is an option to enable an advanced workflow which adds three permissions -- create mailing, schedule mailings, and approve mailings. With that enabled, a scheduled mailing is not necessarily queued to be sent unless it has also been approved. The current scheduled and sent list is where a user with approval permission goes to review and approve a mailing. |
This sounds sensible to me. I'm all for keeping it simple. |
1f39869
to
ee76b19
Compare
6b24c1b
to
8333c05
Compare
Thank you everyone for the feedback. I have rebased & regen'ed & squashed the branch. Ready for merge ;-) |
Word-count of PR change: 4 |
Plus a jig. |
Overview
CiviCRM menus are very pedantic and programmer-oriented (saves a click while testing, but makes you read a lot more).
The CiviMail menu has always made me struggle, with so many technical things in one place, that most admins go and hide under a blanket.
This PR propose a tiny change that I think will not be too polemic:
On the first one, I think we can agree that "unscheduled" is a silly word, and not an actual mailing status.
On the second one, I think most admins, at a glance, won't be confused and think "omg is my scheduled mailing now stuck in the purgatory". In my mind, there are "mailings I'm working on" and "mailings I don't need to worry about".
This PR only affects new installations.
Before
After
Comments