[MAGNOLIA-3845] In activation module, to be able to add "required = true" in the comment box Created: 23/Sep/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: 4.4.2
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Santiago Fernandez de Cordoba Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 1
Labels: activation, security, workflow
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Jackrabbit 1.6.x (Bundle PM)


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   

Now, if you activate something, you are given the option to write a comment and the activation start date, and deactivation date.

We would like to be able to make mandatory to write the comment.

So when somebody activates content, they are obliged to write something, and it makes it easier for everybody to understand what is being activated and proceed with the activation.

Now it does not work if you just add "required = true"

We think it would be a very valuable feature under an editorial point of view.

Thanks



 Comments   
Comment by Magnolia International [ 10/Nov/11 ]

Hi,

Teresa documented a trick to achieve just that on her blog: http://tmiyar.blogspot.com/2011/09/tips-tricks-make-activation-comment.html

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 Mon Feb 12 03:50:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.