2

Page Layout - Arbitrary ordering of groups

I've had a couple of people request the ability to put groups or items on a page layout in a specific order that isn't necessarily a definable pattern like sort ascending or descending.  For instance, if I had a task page grouped by assigned artist, and I want to see the groups in the order of how they sit (thus the order they are visited in rounds).  Would be nice to be able to define a sort either by dragging/dropping groups, or exposing a numeric sort order field that could be adjusted arbitrarily.  Would like something (like sorts) that should be configurable per page, rather than having to create a field on the entity (which would probably work in the lame use case I came up with above).  In some cases it might be useful to be able to order individual records this way too (not just groups), but I've only had specific requests for groups thus far.

4件のコメント

  • 0
    Avatar
    Joe Frayne

    I've experienced this request now as well. Under a shot, they want the tasks to be grouped by type, but they want the groups to be sorted based on the pipeline, rather than alphabetically (Previz, Animation, Lighting, instead of Animation, Lighting, Previz, for example).

  • 0
    Avatar
    Lisakspence

    i've just added an additional field to the task entity for 'sort order', just as is already displayed on the playlist pate.

    it still needs to be updated by hand when things change, but if you generally create your tasks from the task template, you could at least set up a default.

    and i agree, a pulldown option would be nice.

  • 0
    Avatar
    Cam Langs

    All good points. We chatted (with SG) about the notion of a task container. A task container is to tasks as a playlist is to versions. If you look under the hood, playlists have three parts - a playlist, playlist connections and versions. The sort order is not a property of the playlist or the version but instead the playlist connection entity. This key property gets around the issue outlined above -  The sort order is only relevant in a certain context. You don't want to add a field to every task for every potential sorting order (seating order, alphabetical order, people I like the most etc.).

    The item is in the priority stack. If it kills several birds with one stone, the priority could be bumped up (I am only speculating), so chime in if you think it is a good fit.

     

    cheers,

     

    cl

     

  • 0
    Avatar
    Pascal Chappuis

    I'm pinging everybody on this. Has anything like this been implemented somewhere since then ? This would be highly useful. Thank you. P.

     

サインインしてコメントを残してください。