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.

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

Merged
merged 1 commit into from
Oct 31, 2022
Merged

Conversation

mlutfy
Copy link
Member

@mlutfy mlutfy commented Oct 26, 2022

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:

  • "Draft and Unscheduled Mailings" becomes "Draft Mailings"
  • "Scheduled and Sent Mailings" becomes "Sent Mailings"

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

image

After

image

Comments

  • I forgot how to run Regen.
  • The "New Mailing (traditional)" was moved by the ducttape extension.

@civibot
Copy link

civibot bot commented Oct 26, 2022

(Standard links)

@civibot civibot bot added the master label Oct 26, 2022
@shaneonabike
Copy link
Contributor

I also think that the terminology is confusing, and repetitive. A small change but actually super clear and clean.

@larssandergreen
Copy link
Contributor

Definitely +1.

@seamuslee001
Copy link
Contributor

@agileware-justin @johntwyman do either of you have any opinions on this?

@agileware-justin
Copy link
Contributor

agileware-justin commented Oct 26, 2022

@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.

@agileware-justin
Copy link
Contributor

@seamuslee001 I agree with any and all changes to improve the UI.

@agileware-justin
Copy link
Contributor

Whilst we are here, what's with this: New Mailing (Traditional) - who's tradition? Are these based on the beliefs of ancient CiviCRM users? Or perhaps based on some traditional Scottish Jig?

Scottish-Jig-Sending-CiviCRM-Mailing

@johntwyman
Copy link
Contributor

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.

@eileenmcnaughton
Copy link
Contributor

We could word-replace 'traditional' with 'Olde English' maybe?

@yashodha
Copy link
Contributor

@mlutfy +1 on this. You might want to fix generated data as well. Thanks!

@homotechsual
Copy link
Contributor

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.

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

@mlutfy
Copy link
Member Author

mlutfy commented Oct 27, 2022

"This is a very valid point, an unscheduled mailing is absolutely still a draft."

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).

@homotechsual
Copy link
Contributor

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

@lcdservices
Copy link
Contributor

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.

@wmortada
Copy link
Contributor

This sounds sensible to me. I'm all for keeping it simple.

@mlutfy mlutfy force-pushed the menuMailingDrafts branch from 1f39869 to ee76b19 Compare October 30, 2022 17:56
@mlutfy mlutfy force-pushed the menuMailingDrafts branch from 6b24c1b to 8333c05 Compare October 30, 2022 18:03
@mlutfy
Copy link
Member Author

mlutfy commented Oct 30, 2022

Thank you everyone for the feedback.

I have rebased & regen'ed & squashed the branch. Ready for merge ;-)

@colemanw colemanw merged commit 4c93886 into civicrm:master Oct 31, 2022
@colemanw
Copy link
Member

Word-count of PR change: 4
Word-count of PR discussion: 570 🤣

@wmortada
Copy link
Contributor

Plus a jig.

@eileenmcnaughton eileenmcnaughton deleted the menuMailingDrafts branch October 31, 2022 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.