[MGNLEE-420] Edit license data in the About app Created: 16/Nov/15  Updated: 09/Feb/17  Resolved: 08/Jul/16

Status: Closed
Project: Magnolia DX Core
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5

Type: Improvement Priority: Neutral
Reporter: Andreas Weder Assignee: Ngoc Nguyenthanh
Resolution: Fixed Votes: 0
Labels: licence, license, ux
Remaining Estimate: 0d
Time Spent: 4d 7h
Original Estimate: 3d

Issue Links:
Relates
relates to MGNLEE-441 Remove all license data then returns ... Closed
dependency
depends upon MGNLUI-3925 Refactor AboutPresenter to provide ab... Closed
supersession
supersedes MGNLEE-329 Add a dialog to enter a new license Closed
supersedes MGNLEE-327 As an administrator I can see and cha... Closed
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)
Release notes required:
Yes
Date of First Response:
Epic Link: License handling
Sprint: Saigon 51
Story Points: 5

 Description   

In order to enter and edit a product license, administrators have to go to the JCR config tree. This is both error-prone and cumbersome.

We should offer a way to enter, view and validate license data in the "About Magnolia" app. There's a UX concept that describes how this should look and feel.



 Comments   
Comment by Ngoc Nguyenthanh [ 07/Jun/16 ]
Assumption
  • Valid license data: key & owner are not null.

As discussed with mgeljic ejervidalo

  • The license expiration date info: Use read only TextField instead of StaticField due to StaticField is not supported to set property data source. We may introduce a new field for this purpose - need use cases.
  • Delete license feature should do in separated ticket. Follow up ticket: MGNLEE-441
    Removing all license info currently doesn't return to a "degraded" community state, it will eventually prompt the license screen again.
Generated at Mon Feb 12 05:29:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.