[MGNLRES-233] Users should have a way to enable/disable JCR resources in the app Created: 06/Oct/15  Updated: 29/Mar/22  Resolved: 21/Oct/15

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

Type: Story Priority: Neutral
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Won't Do Votes: 0
Labels: pm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLRES-179 Migrate all resources from templates ... Closed
supersession
is superseded by MGNLRES-237 Re-enable a user-interface for proces... 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)
Epic Link: Phase out in-place templating app
Sprint: Basel 15
Story Points: 5
Team: Nucleus

 Description   

For resources which are in JCR
consider sanitizing the bypass property => rename it to enabled (and invert it)
note on UX: naming of this capability should relate well to "overriding?"



 Comments   
Comment by Mikaël Geljić [ 21/Oct/15 ]

This will remain covered in the legacy resources app for the time being (like support for processed-resources). Linking to MGNLRES-237 accordingly.

Generated at Mon Feb 12 06:48:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.