[MGNLACTIVATION-63] New color or icon in admin interface for time-base published pages Created: 06/Aug/08  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Patrick Ehrensperger Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Not relevant


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   

Situation today:
If i schedule a page to publish in the future (time based publishing incl activation), the status of the page in the admin interface remains red. This is confusing because one may think, that the page has not yet been sent through the activation process.

Desired situation:
Time base published pages should have a different color or icon in the status column of the admin interface. This would indicate, that the page has been sent through the activation process, but is not yet active.

Example:
1. Create new page on 2008-08-06 -> status red
2. Set time based publishing date to 2030-08-06 and send the page through the activation process -> status blue (this is the new status that remains until 2030-08-06 and indicates that the page has been sent through the activation process)
3. Automatic time based activation of the page on 2030-08-06 -> status green



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Sun Feb 11 22:59:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.