[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  38  39 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 

Remaining Estimate:
 
 0d 2d 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  37  38 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  36  37 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  35  36 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 
 
 
 
 
 
 
 We currently offer *two ways to add* a new component:* You *click on the "new component" placeholder*.* With an area selected, you *click on the "add component" action*.In both cases, we open a dialog to pick one of the components available in the affected/selected area. The component is then added at the location of the placeholder, which is typically at the end of the list. There's, however, *no way to add a component in other locations of the list, in particular at the beginning* of the list. We'll thus *allow a user to pick one of several, preconfigured locations in the dialog that also asks him or her to pick the type of component to add*. We should support both "at the beginning" and "at the end" for all areas, with "at the end" being the default. If feasible, *allow for the amount and the actual location where new components get added to be configured*.While placeholder can in theory be configured and moved elsewhere (I think there could be several ones), I would not want us to add two placeholders per area to not increase the UI complexity in the page editor ever more. For the same reason, I would not want us to introduce a second "+" (add) icon on the bars itself. UPDATE: Copied from the comments 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 
 
 
 
 
 
 
 We currently offer *two ways to add* a new component:* You *click on the "new component" placeholder*.* With an area selected, you *click on the "add component" action*.In both cases, we open a dialog to pick one of the components available in the affected/selected area. The component is then added at the location of the placeholder, which is typically at the end of the list. There's, however, *no way to add a component in other locations of the list, in particular at the beginning* of the list. We'll thus *allow a user to pick one of several, preconfigured locations in the dialog that also asks him or her to pick the type of component to add*. We should support both "at the beginning" and "at the end" for all areas, with "at the end" being the default. If feasible, *allow for the amount and the actual location where new components get added to be configured*.While placeholder can in theory be configured and moved elsewhere (I think there could be several ones), I would not want us to add two placeholders per area to not increase the UI complexity in the page editor ever more. For the same reason, I would not want us to introduce a second "+" (add) icon on the bars itself.UPDATE: Copied from the comments Here's the clarification, after double-checking with Andreas:* We call for radio options in the {{pages:newComponent}} dialog. This is a relatively cheap solution to let e.g. news editors to add latest articles on top easily.** We acknowledge that we skipped the component dialog (in PAGES-58) when there is only one type of component available; we're ok with this.** We don't show this field for single component areas. * We don't do the secondary split of the "add component" action in the end, not to bloat the action bar.* We consider configuring position of the placeholder(s) on the area definition (cc [~weder] to file a follow-up issue).Anything I missed? Reopening/updating this issue; I will also decline the current PR. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 
 
 
 
 
 
 
 We currently offer *two ways to add* a new component:* You *click on the "new component" placeholder*.* With an area selected, you *click on the "add component" action*.In both cases, we open a dialog to pick one of the components available in the affected/selected area. The component is then added at the location of the placeholder, which is typically at the end of the list. There's, however, *no way to add a component in other locations of the list, in particular at the beginning* of the list. We'll thus *allow a user to pick one of several, preconfigured locations in the dialog that also asks him or her to pick the type of component to add*. We should support both "at the beginning" and "at the end" for all areas, with "at the end" being the default. If feasible, *allow for the amount and the actual location where new components get added to be configured*.While placeholder can in theory be configured and moved elsewhere (I think there could be several ones), I would not want us to add two placeholders per area to not increase the UI complexity in the page editor ever more. For the same reason, I would not want us to introduce a second "+" (add) icon on the bars itself.*UPDATE*: Copied from the commentsHere's the clarification, after double-checking with Andreas:* We call for radio options in the {{pages:newComponent}} dialog. This is a relatively cheap solution to let e.g. news editors to add latest articles on top easily.** We acknowledge that we skipped the component dialog (in PAGES-58) when there is only one type of component available; we're ok with this.** We don't show this field for single component areas. * We don't do the secondary split of the "add component" action in the end, not to bloat the action bar.* We consider configuring position of the placeholder(s) on the area definition * Added a wireframe showing the radio button group for picking where to add the component (at the beginning or at the end).* As a side note, you'll notice I've also renamed the dialog title and the label of the first input field to be more in-line with what we have elsewhere. If that's easy to change in one go, please do so, else feel free to create a follow-up issue for these label changes. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
  

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Comment:
 
 [~ngoc.nguyenthanh] [~mgeljic] I've seen that you've created two actions "add at the top" and "add at the bottom", with the default action being "add at the bottom".I agree with @mika and [~ejervidalo] we should only have a single action in the Action bar called "Add component" for the time being, which by default adds the component after the last component - I would not show both actions in the Action bar. However, I suggest we *keep both actions*, now that we have them, so that *customers could change their configuration to provide the "add at the top" action instead or even configure both*, if their project would require that. WDYT? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 

Release notes required:
 
 Yes 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[JIRA (on behalf of Andreas Weder)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Weder updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andreas Weder 
 
 
 
 
 
 
 
 
 
 We currently offer *two ways to add* a new component:* You *click on the "new component" placeholder*.* With an area selected, you *click on the "add component" action*.In both cases, we open a dialog to pick one of the components available in the affected/selected area. The component is then added at the location of the placeholder, which is typically at the end of the list. There's, however, *no way to add a component in other locations of the list, in particular at the beginning* of the list. We'll thus *allow a user to pick one of several, preconfigured locations in the dialog that also asks him or her to pick the type of component to add*. We should support both "at the beginning" and "at the end" for all areas, with "at the end" being the default. If feasible, *allow for the amount and the actual location where new components get added to be configured*.While placeholder can in theory be configured and moved elsewhere (I think there could be several ones), I would not want us to add two placeholders per area to not increase the UI complexity in the page editor ever more. For the same reason, I would not want us to introduce a second "+" (add) icon on the bars itself. -However, splitting the current "add component" action into two - "add component at top" and "add component at bottom" sounds like an additional, good thing to have.- 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Labels:
 
 blocked estimate-with-uncertainty  is-time-consuming page-editor pain-point quickwin user-feedback ux 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 We currently offer *two ways to add* a new component:* You *click on the "new component" placeholder*.* With an area selected, you *click on the "add component" action*.In both cases, we open a dialog to pick one of the components available in the affected/selected area. The component is then added at the location of the placeholder, which is typically at the end of the list. There's, however, *no way to add a component in other locations of the list, in particular at the beginning* of the list. We'll thus *allow a user to pick one of several, preconfigured locations in the dialog that also asks him or her to pick the type of component to add*. We should support both "at the beginning" and "at the end" for all areas, with "at the end" being the default. If feasible, *allow for the amount and the actual location where new components get added to be configured*.While placeholder can in theory be configured and moved elsewhere (I think there could be several ones), I would not want us to add two placeholders per area to not increase the UI complexity in the page editor ever more. For the same reason, I would not want us to introduce a second "+" (add) icon on the bars itself. - However,  * splitting the current "add component" action into two - "add component at top" and "add component at bottom" *  sounds like an additional, good thing to have. - 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
  

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Status:
 
 pre-integration QA Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  34  35 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 
 
Andreas Weder While tackling this, another action was added to the action bar. It seems that was not the original intent, rather have a second button on the add component dialog footer only? Besides, from the comments we don't know if that has changed in the meantime; Espen Jervidalo rightfully pointed out that we're starting to clutter the action bar even more, that's why I'm asking for confirmation there. 
The thing is, it also kinda conflicts with 

PAGES-58
: how does one add a component to the top when there is only one available component? Do we skip it for the sake of clarity? 
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Labels:
 
 blocked estimate-with-uncertainty is-time-consuming page-editor pain-point quickwin user-feedback ux 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
   

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  33  34 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 

Fix Version/s:
 
 5.4.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 

Fix Version/s:
 
 5.4.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Fix Version/s:
 
 5.4.5 
 
 
 

Fix Version/s:
 
 5.4.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  32  33 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[on behalf of Mikaël Geljić]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mikaël Geljić updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mikaël Geljić 
 
 
 

Sprint:
 
 Saigon  31  32 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 

Affects Version/s:
 
 5.4.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 

Fix Version/s:
 
 5.4.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 

Original Estimate:
 
 4d 
 
 
 

Remaining Estimate:
 
 4d 
 
 
 

Account:
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[JIRA (on behalf of Ngoc Nguyenthanh)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ngoc Nguyenthanh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ngoc Nguyenthanh 
 
 
 

Assignee:
 
 Ngoc Nguyenthanh 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-59) Allow to add components also at the top of an area

[on behalf of Roman Kovařík]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Roman Kovařík updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Magnolia pages module /  PAGES-59 
 
 
 
  Allow to add components also at the top of an area  
 
 
 
 
 
 
 
 
 

Change By:
 
 Roman Kovařík 
 
 
 

Project:
 
 Magnolia  UI  pages module 
 
 
 

Key:
 
 MGNLUI PAGES - 3692 59 
 
 
 

Security:
 
 Public 
 
 
 

Component/s:
 
 page editor 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: