[PAGES-307] Area with only one available component shows option to choose component Created: 11/Jun/20  Updated: 14/Sep/22  Resolved: 13/Aug/20

Status: Closed
Project: Magnolia pages module
Component/s: Pages app
Affects Version/s: 6.2.1
Fix Version/s: 6.2.3

Type: Improvement Priority: Neutral
Reporter: Tomáš Gregovský Assignee: Martin Haderka
Resolution: Fixed Votes: 0
Labels: 622
Remaining Estimate: Not Specified
Time Spent: 1h 16m
Original Estimate: Not Specified

Issue Links:
Relates
relates to PAGES-245 Missing default value for component p... Closed
causality
is causing PAGES-330 When only one component is available ... Closed
duplicate
is duplicated by PAGES-295 If only one type of component availab... Closed
relation
is related to MGNLUI-6000 Make single available component being... Closed
is related to PAGES-849 Create Page: Template on top of the l... Open
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:
Epic Link: UI framework implementation
Sprint: UI FW 8
Story Points: 3

 Description   

after migration from 5.7 to 6.2.1 area with only one available component shows option to choose component without selecting it automatically. This force editor to make extra 3 clicks compared to m5.7, where in case of only one component, editor wasn't asked which one to choose, but was directly taken to edit such component.

you can see it recorded here: https://drive.google.com/file/d/1f056NykcoMApIDgxXwq2qInV3rd6aMip/view?usp=sharing



 Comments   
Comment by Christopher Chard [ 15/Jul/20 ]

+1 for this

Comment by Šimon Demočko [ 23/Jul/20 ]

The drive video is unavailable for viewing for magnolia accounts

Comment by Šimon Demočko [ 12/Aug/20 ]

QA results: Only preselection of the value was implemented. The dialog still opens, but only confirmation is necessary, selection is there. PR noted implementing dialog skipping would be non-trivial. If necessary, followup ticket can be created.

Comment by Christopher Chard [ 12/Aug/20 ]

Hi Simon,

that is quite fine as usability-wise it might be easier for the editor to understand what is actually happening.

He adds a component, the dialog "open component" opens, he might check his options if curious ("oh, only one option, ok") and add it.
In editor trainings I found that some people were confused when the dialog was skipped.

So pre-selection is great. Thank you!

Kind regards,
Chris

Comment by Martin Haderka [ 13/Aug/20 ]

Reopen:

Position field selection is empty, even if default value is provided.

Comment by Šimon Demočko [ 13/Aug/20 ]

mhaderka That's already a different ticket PAGES-245

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