[MGNLWORKFLOW-174] Schedule activation of content based on named releases instead of just raw dates Created: 27/Nov/13  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia Workflow Module
Component/s: None
Affects Version/s: 5.2
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

In 4.5 you can schedule activation on a page (and its children) by specifying a raw date. It would be convenient if editors could create "releases" with a name and a date. And then when they could specify this release when they activate content. This way many different content items could be scheduled to be released at the same time. And the time for this release could be changed by only editing the "release".

Use case:
Consider a company planning a campaign or an update of many parts of its website, related to events or seasonal activities. Maybe they want to plan and develop new "releases" of the website for weekly or daily updates far ahead of time.

(Inspired by video on prismic.io cms website https://prismic.io/)

I wouldnt want to make it any harder to schedule content to be released in the future - so this could either be in addition to being able to just add a date - or a "release" could be created automatically with an auto-generated default name if you just specify a date.



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 10:07:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.