Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 930
    • Issues 930
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • Core
  • Issues
  • #873

Closed
Open
Opened Apr 13, 2019 by totten@tottenOwner

Mosaico A/B testing for "Subject" line

This is catch-all issue for linking together various changes in https://github.com/veda-consulting/uk.co.vedaconsulting.mosaico/ and https://github.com/civicrm/civicrm-core.

General goal

When composing a new mailing in Mosaico, allow the user to enter multiple subject lines. Each subject will be delivered to a different set of users as part of an A/B test.

Related documents

  • Wiki: ABn testing v2: This is a specification developed at a previous sprint near Cologne, DE. This issue is targetting the same UI spec, and some of the data-structures anticipate the ABn v2, but it only tackles Mosaico Subject UI - not all the other requirements.
  • Gist: Mosaico A/B planning: Comparison of a few project plans (tasks, trade-offs, etc). We're pursuing A2.

Exploratory branches

The purpose of an exploratory branch is to allow varied experimentation (tweaking multiple parts with the aim of reaching a cogent/working approach) before submitting each individual change to the full review. Exploratory branches may have frequent/unplanned changes (rebasing, squashing, more commits, etc).

There are a couple exploratory branches:

  • https://github.com/totten/civicrm-core/tree/5.7-mosaico-ab-exp
  • https://github.com/totten/uk.co.vedaconsulting.mosaico/tree/2.x-ab

Pull Requests

As specific items from the exploratory changes firm up, they're submitted as full PRs.

  • 14044: CiviUnitTestCase - Extract traits to facilitate extension testing
  • 14045: MailingAB - Migrate "copy winner" logic from JS to PHP
  • 14047: civi.api.prepare - Allow dynamic wrappers
Edited Apr 13, 2019 by totten
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#873