I suggest you ...

Move card to another project

There's a really handy feature on Kantree (that I like a lot) that is applying an automated task on a column that is reflected on all the cards within it (and cards that, after this automation is created, are moved to this column).
One feature that is missing (and we see that it can be done quite easily on other task managers) is an automated task that moves the cards within a column (group) to another project, that would be really handy.

It would work like this:
Click on the cog to configure list, Click "set context for all cards" and, from here, the option to select the project would be available.

Can this be done? It would be very handy

6 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Tiago Melo shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • Emmanuel commented  ·   ·  Flag as inappropriate

    If implemented, perhaps it could be more handy for everyone to add an option on that automated task to create mirror card on another project in spite of moving it ? (Or doing two automated tasks)

    Think it would ease a lot the work of some of us to have those mirror cards created automatically...

  • Tiago Melo commented  ·   ·  Flag as inappropriate

    Jérôme, sorry to take that long to respond this (I've been working a lot lately) but you are correct; what I want to achieve is move cards freely between projects.
    For example: let's say I have 2 projects:

    Project A
    Project B

    Let's now say that these projects are, somewhat, linked and it comes to a point that a card created in B should now be in A, so it would make sense to just move it: it would not exist in B anymore, cause I've moved it to A.

    The other way around should also be possible, as I could create a Card on A, and by some reason, it should be moved to B

  • Manuel Renz commented  ·   ·  Flag as inappropriate

    I like this idea but when moving or mirroring you have to be thoughtfull about what exactly happens to the applied models.

    I currently do something similar by applying another context group. for each context I have a separate view. This way it looks like another Board but it truely isnt. This way the cards do not change their ID regardless what processs stage the card is moved to.
    In my case I have A Sales Board with three contexts groups. Leads, Opportunities and Orders. when a Lead is moved to the succesfull group it automatically is added to a group of the Opportunities context and so on...

  • Tiago Melo commented  ·   ·  Flag as inappropriate

    Hello Jérôme
    That's exactly what I want to achieve because the way I and my team use Kantree.
    We have a project for Inbox and categorize it there; then, once this is done, we move to our workable items (or focus).
    What isn't important we let at the INBOX board

  • AdminJérôme (Support Team, Kantree) commented  ·   ·  Flag as inappropriate

    Hi Tiago,

    I want to be sure to understand this.

    You want to move a card in another project when dropping it a column. If we do this, you do understand that the card won't be available anymore in the source project (in which you perform the drop). Is this what you want to achieve ?

    Another possibility would be to have an automated task that creates a card link (or mirror) in another project.


Feedback and Knowledge Base