Pocket ListsQuestions

Moving items

Can I move/copy items from one list to another?

Posted: August 12, 2019

2 answers

  • vofka staff August 12, 2019 08:53

    Sure! Here is a short note on how to move items from one list to another: https://pocketlists.com/help/8/moving-to-dos/

    Copying is not possible at the moment, but you may duplicate (clone) a list when needed — swipe over a list from right to left and tap on a green duplicate button.

  • Gino Bonetti August 19, 2019 12:52

    This does not seem to work for a shared list, as I am only seeing the trash bin when swiping right to left. Is there any other way or am I missing something?

    Best,

    Dennis

    • vofka vofka staff August 19, 2019 13:36

      Yes, you are right. Items may not be moved outside a shared to-do list due to access right issues. The cloud sync provides a security layer that checks which to-do lists (and items) a user can access, and there are multiple issues occur when an item is being moved from one shared list (which a certain group of users can access) to another private/shared list with different sharing settings and a different group of users.

      We'll update the main article on this issue. Thanks for the comment!

      In future app updates, we will investigate how to improve the sync so that item re-location across lists won't interfere with the access rights security layer.

      • Mark Cicoria Mark Cicoria August 19, 2019 13:58

        Hi there. This is definitely something that will be make or break for us as we are using lists to prioritize and assign. Not being able to easily move an item from a shared list to another shared list (with the same person) makes it very difficult to create a workflow. 

        Do you happen to know when this might be available? 

        As for a technical solution, could you run the same operations that already exist?

        On the list where the task current is: delete op

        On the target list: create op, (edit op if needed) 

        Seems reasonable from a permissions standpoint, not having delete or create permission would trigger an existing fail case. 

        On the backend I would assume this should create a new item so that new rights are assigned and the item that was “moved” can be properly restored should another user desire. 

        Cheers. 

This question has been automatically archived because there were over 30 days of inactivity. Posting new comments is disabled. Start a new topic instead.