Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Medium Medium
    • Resolution: Duplicate
    • Affects Version/s: 2.1.0-rc1
    • Fix Version/s: n/a
    • Component/s: None
    • Labels:

      Description

      As a user I expect that URL aliases will be sorted. I've attached a screenshot - I was adding items in order: abc, def, a, b, c, d... and it is not sorted at all.

        Issue Links

          Activity

          Barbara Grajczyk created issue -
          Hide
          Dawid Parafiński added a comment -

          Sylvain Guittard
          Inaki Juaniz-Velilla
          Any insight how this should be handled? Right now i just sorted them by url name but maybe they should also by grouped by languages on that list If that, what should be the order of those?
          And what about sorting system url aliases?

          Show
          Dawid Parafiński added a comment - Sylvain Guittard Inaki Juaniz-Velilla Any insight how this should be handled? Right now i just sorted them by url name but maybe they should also by grouped by languages on that list If that, what should be the order of those? And what about sorting system url aliases?
          Dawid Parafiński made changes -
          Field Original Value New Value
          Assignee Dawid Parafiński [ david.parafinski@ez.no ]
          Dawid Parafiński made changes -
          Status Open [ 1 ] Confirmed [ 10037 ]
          Hide
          Sylvain Guittard added a comment -

          Thanks Dawid Parafiński for asking.
          I think sorting by URL should be enough.
          But your question about grouping by language is interesting. We should bring the sort feature (the one on sub-items list) to this table. So users will be able to access faster the URL they are looking for.
          Problem: sub-items list is a react component, it might not be interesting to reuse this component and I am sure we have other options. What do you think [~piotr.nalepa@ez.no] Dariusz Szut?

          Show
          Sylvain Guittard added a comment - Thanks Dawid Parafiński for asking. I think sorting by URL should be enough. But your question about grouping by language is interesting. We should bring the sort feature (the one on sub-items list) to this table. So users will be able to access faster the URL they are looking for. Problem: sub-items list is a react component, it might not be interesting to reuse this component and I am sure we have other options. What do you think [~piotr.nalepa@ez.no] Dariusz Szut ?
          Hide
          Piotr Nalepa (Inactive) added a comment -

          It shouldn't take too much effort to implement sorting on the frontend side. We should consider adding the sortable features in other places as well. I believe it should be considered as another story with a list of all places where sortable tables should be implemented (with exception for Sub Items module).

          Show
          Piotr Nalepa (Inactive) added a comment - It shouldn't take too much effort to implement sorting on the frontend side. We should consider adding the sortable features in other places as well. I believe it should be considered as another story with a list of all places where sortable tables should be implemented (with exception for Sub Items module).
          Hide
          Sylvain Guittard added a comment -

          Thanks [~piotr.nalepa@ez.no]. We will work on that

          Show
          Sylvain Guittard added a comment - Thanks [~piotr.nalepa@ez.no] . We will work on that
          Sylvain Guittard made changes -
          Link This issue relates to EZP-29063 [ EZP-29063 ]
          Sylvain Guittard made changes -
          Link This issue relates to EZP-29064 [ EZP-29064 ]
          Hide
          Sylvain Guittard added a comment -

          Follow-up stories:

          Show
          Sylvain Guittard added a comment - Follow-up stories: EZP-29063 EZP-29064
          Dawid Parafiński made changes -
          Status Confirmed [ 10037 ] Backlog [ 10000 ]
          Dawid Parafiński made changes -
          Status Backlog [ 10000 ] InputQ [ 10001 ]
          Dawid Parafiński made changes -
          Status InputQ [ 10001 ] Development [ 3 ]
          Hide
          Dawid Parafiński added a comment - - edited

          Sylvain Guittard
          I assume this is now resolved as won't do in favour of EZP-29063 and should be closed?

          Show
          Dawid Parafiński added a comment - - edited Sylvain Guittard I assume this is now resolved as won't do in favour of EZP-29063 and should be closed?
          Hide
          Sylvain Guittard added a comment - - edited

          You submitted a PR for sorting the URL table. I don't think we can mark this issue as won't do. I would recommend Fixed.

          Show
          Sylvain Guittard added a comment - - edited You submitted a PR for sorting the URL table. I don't think we can mark this issue as won't do . I would recommend Fixed .
          Hide
          Dawid Parafiński added a comment -

          Sylvain Guittard
          Thing is, in order to do it correctly it must be done across two repositories (not in like proposed PR, it turns out adding sorting would be a BC break in that case). don't know then, if this should be done just to be overwritten by frontend sorting.

          Show
          Dawid Parafiński added a comment - Sylvain Guittard Thing is, in order to do it correctly it must be done across two repositories (not in like proposed PR, it turns out adding sorting would be a BC break in that case). don't know then, if this should be done just to be overwritten by frontend sorting.
          Hide
          Sylvain Guittard added a comment -

          I understand. The stories EZP-29063, EZP-29064 will be for next sprint of the one after. So maybe it's better to close your PR and close this issue.

          Show
          Sylvain Guittard added a comment - I understand. The stories EZP-29063 , EZP-29064 will be for next sprint of the one after. So maybe it's better to close your PR and close this issue.
          Dawid Parafiński made changes -
          Status Development [ 3 ] Development Review [ 10006 ]
          Show
          Dawid Parafiński added a comment - https://jira.ez.no/browse/EZP-29063
          Dawid Parafiński made changes -
          Assignee Dawid Parafiński [ david.parafinski@ez.no ]
          Status Development Review [ 10006 ] Closed [ 6 ]
          Fix Version/s n/a [ 14929 ]
          Resolution Duplicate [ 3 ]
          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Confirmed Confirmed
          6d 16h 17m 1 david.parafinski@ez.no 30/Mar/18 9:45 AM
          Confirmed Confirmed Backlog Backlog
          5d 23h 52m 1 david.parafinski@ez.no 05/Apr/18 9:37 AM
          Backlog Backlog InputQ InputQ
          1m 40s 1 david.parafinski@ez.no 05/Apr/18 9:39 AM
          InputQ InputQ Development Development
          14s 1 david.parafinski@ez.no 05/Apr/18 9:39 AM
          Development Development Development Review Development Review
          23h 47m 1 david.parafinski@ez.no 06/Apr/18 9:26 AM
          Development Review Development Review Closed Closed
          2m 3s 1 david.parafinski@ez.no 06/Apr/18 9:28 AM

            People

            • Assignee:
              Unassigned
              Reporter:
              Barbara Grajczyk
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: