Duplicate campaign (to allow for repeat publish)

[chillu]

Overview

Most campaigns are expected to be one-off events (e.g. "new office location"), but some will require repeat publications (e.g. "monthly job title reviews on staff pages").

Acceptance Criteria

• I can duplicate a campaign including all explicit and implicit records
• The owner of the campaign is changed to the user triggering the duplication
• If new draft versions have been created of the included records, the "before" version is updated accordingly
• If included records have been deleted in the meantime, they're silently removed from the duplicated campaign (or at least don't cause errors on publishing the new campaign)
• The creation date is updated
• Duplication can be actioned on campaigns with are either already published or not published yet

Excluded

• The datamodel does not need to link the duplicated campaign back to the original

[clarkepaul]

Suggestion for implementation @tractorcow @chillu

[clarkepaul]

I feel we need to update the "Last published" column now to a status column eg. Status (Open, Published) as well as a disabled look for campaigns which have already been published.

[sminnee]

A few thoughts:

• Is this important as a 4.0 feature?
• Do we have reports from users / user-testing that elaborates on why this feature is important?
• Would it be better to work with someone using campaigns in production to understand what's needed here?

[chillu]

I'm keen to see more actual use of campaigns before we get into the "repeat publish" use case. It's a bit of a chicken and egg case: We need to get campaigns baseline useful for people to actually start using it and figure out where it doesn't work for them. So it'll need good feedback loops to stay on top of that. Note that this issue currently isn't assigned to a milestone.

[sminnee]

@chillu impact/low, then? I just updated.

[clarkepaul]

Impact medium I would have thought.

[chillu]

Have set back to medium then :)

[newleeland]

Potential Prototype

https://invis.io/8HD9ADEPR#/250964968_Campaigns_-_List_-_Dashboard_V2

Would there be a case for having a "disabled" Campaign? @clarkepaul

[chillu]

@newleeland Nice and simple. I like that it just appends " copy", rather than having us code yet another dialog for the new name. The animated row highlight makes it clear enough in my opinion. I assume the "released/unreleased" column designs are targeted at another card, not this one here?

[clarkepaul]

@newleeland cheers for making the updates, I actually did the same changes except I was thought "Released" worked well but not "Unreleased", in the end I still opted for "Active" and "Published".

[newleeland]

@clarkepaul Just did a lean UX test with the names. We ended up settling on status types "Work in progress" and "Published" (as it corresponds to the publish button). Here is the new prototype:
https://invis.io/8HD9ADEPR#/250964968_Campaigns_-_List_-_Dashboard_V2

[newleeland]

@clarkepaul I've updated the prototype with the new wording from a quick Lean user test. For words campaigns that are still working on will be Working in progress, and campaigns released to the web will be Published to align to the Publish button within individual campaigns.

@chillu We could put this into another card, it's not that much work to change the names and add a coloured circle on the left side of the text?

[chillu]

@newleeland I've added it to a separate card - this allows us to prioritise this individually: #53