[Feature Request] Copy card #39

Closed
opened 2026-02-04 16:42:41 +03:00 by OVERLORD · 28 comments
Owner

Originally created by @zahidhanif on GitHub (Oct 28, 2020).

Thanks for this brilliant app. I am currently self-hosting in docker.

Please allow users to copy a card, including tasks. I use templates so this would be very helpful.

Thanks again.

Originally created by @zahidhanif on GitHub (Oct 28, 2020). Thanks for this brilliant app. I am currently self-hosting in docker. Please allow users to copy a card, including tasks. I use templates so this would be very helpful. Thanks again.
OVERLORD added the enhancementgood first issue labels 2026-02-04 16:42:41 +03:00
Author
Owner

@meltyshev commented on GitHub (Nov 5, 2020):

It's a good feature. I will add it soon.

@meltyshev commented on GitHub (Nov 5, 2020): It's a good feature. I will add it soon.
Author
Owner

@nickbe commented on GitHub (Nov 8, 2020):

I don't think a simple "copy card" feature would be too useful. At some point we'll rather need a proper template management: For boards and for cards. That way you would be able to "create card/board from ". But I think this will be on the list at a later point 😀

@nickbe commented on GitHub (Nov 8, 2020): I don't think a simple "copy card" feature would be too useful. At some point we'll rather need a proper template management: For boards and for cards. That way you would be able to "create card/board from <template>". But I think this will be on the list at a later point 😀
Author
Owner

@zahidhanif commented on GitHub (Nov 9, 2020):

My suggestion was not for a template management workflow as I understand that will take longer to implement. I was suggesting a simply copy card like in Trello where you can copy a card plus the sub-tasks. This is available on similar card/board systems such as kanboard (I tried this as well as Planka). I was hoping this would be simple to implement.

@zahidhanif commented on GitHub (Nov 9, 2020): My suggestion was not for a template management workflow as I understand that will take longer to implement. I was suggesting a simply copy card like in Trello where you can copy a card plus the sub-tasks. This is available on similar card/board systems such as kanboard (I tried this as well as Planka). I was hoping this would be simple to implement.
Author
Owner

@fanofnarendra commented on GitHub (Apr 2, 2021):

Hey, Can I work on this. I have an idea for this

@fanofnarendra commented on GitHub (Apr 2, 2021): Hey, Can I work on this. I have an idea for this
Author
Owner

@meltyshev commented on GitHub (Apr 2, 2021):

Sure, pull requests are always welcome!

@meltyshev commented on GitHub (Apr 2, 2021): Sure, pull requests are always welcome!
Author
Owner

@fanofnarendra commented on GitHub (Apr 14, 2021):

Hey I have 2 options in mind:

1: The pencil icon in every card there I can give an option for copy and then in the modal give options on which list we can copy
2: To have a copy icon near pencil and then once the user clicks it the copy happens and enable paste option near pencil icon of each list title
3: To have a copy icon near pencil and then once the user clicks it the copy happens and they can even drag it to corresponding list. If the copy is enables its copy otherwise its a move. Which one is a good idea??

@fanofnarendra commented on GitHub (Apr 14, 2021): Hey I have 2 options in mind: 1: The pencil icon in every card there I can give an option for copy and then in the modal give options on which list we can copy 2: To have a copy icon near pencil and then once the user clicks it the copy happens and enable paste option near pencil icon of each list title 3: To have a copy icon near pencil and then once the user clicks it the copy happens and they can even drag it to corresponding list. If the copy is enables its copy otherwise its a move. Which one is a good idea??
Author
Owner

@zahidhanif commented on GitHub (Apr 14, 2021):

I like option 1 as it similar to how Trello works

@zahidhanif commented on GitHub (Apr 14, 2021): I like option 1 as it similar to how Trello works
Author
Owner

@nickbe commented on GitHub (Apr 18, 2021):

Although we want a copy option too it should definetely NOT be like Trello, but differently - better.

@nickbe commented on GitHub (Apr 18, 2021): Although we want a copy option too it should definetely NOT be like Trello, but differently - better.
Author
Owner

@zahidhanif commented on GitHub (Apr 18, 2021):

I understand you want it to be better than Trello @nickbe but to help @fanofnarendra include this feature, how do you think he should implement it?

@zahidhanif commented on GitHub (Apr 18, 2021): I understand you want it to be better than Trello @nickbe but to help @fanofnarendra include this feature, how do you think he should implement it?
Author
Owner

@nickbe commented on GitHub (Apr 18, 2021):

I was thinking about this yesterday and the best idea so far seems one that was discussed some time ago:

  1. First mark the card and show it in some sort of thumbnail list (maybe at the botton or right side of the view)
    This could be done either for copying, moving or just remembering (starring) cards and quickjumping

  2. Then when creating a new card have an option to pastemove OR copy from a jumplist card
    (small menue on thumbnail)

This way we would have a practical multi purpose control.

@nickbe commented on GitHub (Apr 18, 2021): I was thinking about this yesterday and the best idea so far seems one that was discussed some time ago: 1. First mark the card and show it in some sort of thumbnail list (maybe at the botton or right side of the view) This could be done either for copying, moving or just remembering (starring) cards and quickjumping 2. Then when creating a new card have an option to pastemove OR copy from a jumplist card (small menue on thumbnail) This way we would have a practical multi purpose control.
Author
Owner

@zahidhanif commented on GitHub (Apr 18, 2021):

That's an interesting idea but from a UX point of view, it's very different to the current interface. Currently, all card actions are driven by clicking the pencil in the top right of the card (such as Move and Delete). A logical place for a Copy function would be to add to this menu rather trying to create a new UI element such jump list or thumbnail list. Just my opinion as that makes sense to me but as @fanofnarendra is coding this, I am sure he has his own ideas too.

@zahidhanif commented on GitHub (Apr 18, 2021): That's an interesting idea but from a UX point of view, it's very different to the current interface. Currently, all card actions are driven by clicking the pencil in the top right of the card (such as Move and Delete). A logical place for a Copy function would be to add to this menu rather trying to create a new UI element such jump list or thumbnail list. Just my opinion as that makes sense to me but as @fanofnarendra is coding this, I am sure he has his own ideas too.
Author
Owner

@nickbe commented on GitHub (May 11, 2021):

Cool.

@nickbe commented on GitHub (May 11, 2021): Cool.
Author
Owner

@Riya123-code commented on GitHub (Sep 6, 2022):

Can i work on this enhancement?

@Riya123-code commented on GitHub (Sep 6, 2022): Can i work on this enhancement?
Author
Owner

@meltyshev commented on GitHub (Sep 6, 2022):

Yes, sure! I planned to do this as my next task, but then I'll just skip it. If you need help, you can ask me.

@meltyshev commented on GitHub (Sep 6, 2022): Yes, sure! I planned to do this as my next task, but then I'll just skip it. If you need help, you can ask me.
Author
Owner

@Riya123-code commented on GitHub (Oct 12, 2022):

Will it be fine if i give copy and paste option to every card ? like clicking the pencil on the top right of the card and providing option of copy and paste .

@Riya123-code commented on GitHub (Oct 12, 2022): Will it be fine if i give copy and paste option to every card ? like clicking the pencil on the top right of the card and providing option of copy and paste .
Author
Owner

@meltyshev commented on GitHub (Oct 12, 2022):

Yep, it will be fine

@meltyshev commented on GitHub (Oct 12, 2022): Yep, it will be fine
Author
Owner

@Riya123-code commented on GitHub (Oct 13, 2022):

Can i get an approval on whether i am assigned this task so that i can start working on it.

@Riya123-code commented on GitHub (Oct 13, 2022): Can i get an approval on whether i am assigned this task so that i can start working on it.
Author
Owner

@meltyshev commented on GitHub (Oct 14, 2022):

Sure, you are assigned this task 🙂

@meltyshev commented on GitHub (Oct 14, 2022): Sure, you are assigned this task 🙂
Author
Owner

@Riya123-code commented on GitHub (Oct 17, 2022):

first of all thanks for assigning me this task.
Is there any project related specific group to discuss errors or doubts ?

@Riya123-code commented on GitHub (Oct 17, 2022): first of all thanks for assigning me this task. Is there any project related specific group to discuss errors or doubts ?
Author
Owner

@meltyshev commented on GitHub (Oct 17, 2022):

Unfortunately no, you can text me on Telegram (username: gh0st1y) and I'll try to help. I'll be sure to add a place for discussions soon.

@meltyshev commented on GitHub (Oct 17, 2022): Unfortunately no, you can text me on Telegram (username: gh0st1y) and I'll try to help. I'll be sure to add a place for discussions soon.
Author
Owner

@leguennecj commented on GitHub (Jun 21, 2023):

Hello how to copy cards ?

@jensfrost @meltyshev @nickbe @Riya123-code @fanofnarendra @zahidhanif

@leguennecj commented on GitHub (Jun 21, 2023): Hello how to copy cards ? @jensfrost @meltyshev @nickbe @Riya123-code @fanofnarendra @zahidhanif
Author
Owner

@gorrilla10101 commented on GitHub (Sep 10, 2023):

@jensfrost my two cents is if you have an implementation that works then go ahead and do a pull request. This allows the maintainers who actually know the ins and outs to weigh in on what you have done and for you to address any issues they notice while bringing an important feature to planka. Currently it might not be great, when it's approved you will at least know it's passable, and if you abandon it then someone else can build from where you are.

Food for thought, you currently have a working solution for the issue with the most comments. Also I went through your implementation and nothing leapt out as an issue.

@gorrilla10101 commented on GitHub (Sep 10, 2023): @jensfrost my two cents is if you have an implementation that works then go ahead and do a pull request. This allows the maintainers who actually know the ins and outs to weigh in on what you have done and for you to address any issues they notice while bringing an important feature to planka. Currently it might not be great, when it's approved you will at least know it's passable, and if you abandon it then someone else can build from where you are. Food for thought, you currently have a working solution for the issue with the most comments. Also I went through your implementation and nothing leapt out as an issue.
Author
Owner

@Bonnix82 commented on GitHub (Oct 25, 2023):

The function "Copy card" would be really a nice feature for this great app.

@Bonnix82 commented on GitHub (Oct 25, 2023): The function "Copy card" would be really a nice feature for this great app.
Author
Owner

@Istria1704 commented on GitHub (Mar 12, 2024):

Hi all,

Any updates on the "copy/duplicate card" feature?

I was thinking it could be an exact copy of the "move" functionality. Except that it would not delete the card in the old location.

@Istria1704 commented on GitHub (Mar 12, 2024): Hi all, Any updates on the "copy/duplicate card" feature? I was thinking it could be an exact copy of the "move" functionality. Except that it would not delete the card in the old location.
Author
Owner

@meltyshev commented on GitHub (Mar 12, 2024):

Hi!

Any updates on the "copy/duplicate card" feature?

Adding this is certainly in our plans, but right now we're trying to rework more basic things like proper data deletion. Since I'm the only developer in the team, adding new features takes a looot of time, but we're in the active phase of solving this problem and things will probably be much faster in the near future.

I was thinking it could be an exact copy of the "move" functionality. Except that it would not delete the card in the old location.

Copying is a little more complicated than moving, because when you move a card you just need to change boardId and listId, but when you copy it you need to duplicate the data and also create a copy of the attachments.

@meltyshev commented on GitHub (Mar 12, 2024): Hi! > Any updates on the "copy/duplicate card" feature? Adding this is certainly in our plans, but right now we're trying to rework more basic things like proper data deletion. Since I'm the only developer in the team, adding new features takes a looot of time, but we're in the active phase of solving this problem and things will probably be much faster in the near future. > I was thinking it could be an exact copy of the "move" functionality. Except that it would not delete the card in the old location. Copying is a little more complicated than moving, because when you move a card you just need to change boardId and listId, but when you copy it you need to duplicate the data and also create a copy of the attachments.
Author
Owner

@Istria1704 commented on GitHub (Mar 12, 2024):

Thanks for the update!
No rush. I understand it takes time with a small (one man) dev team.

I thought "moving" was basically copying, with the addition of deleting the original. But I understand now it works differently. So I guess it's not an easy copy/paste implementation.

I'll just patiently wait for it to be added. =) Thanks again for all the work. Planka is awesome. =)

@Istria1704 commented on GitHub (Mar 12, 2024): Thanks for the update! No rush. I understand it takes time with a small (one man) dev team. I thought "moving" was basically copying, with the addition of deleting the original. But I understand now it works differently. So I guess it's not an easy copy/paste implementation. I'll just patiently wait for it to be added. =) Thanks again for all the work. Planka is awesome. =)
Author
Owner

@CodeNamedRobin commented on GitHub (Jul 23, 2024):

Why isn't this closed?

@CodeNamedRobin commented on GitHub (Jul 23, 2024): Why isn't this closed?
Author
Owner

@daniel-hiller commented on GitHub (Jul 23, 2024):

Because nobody closed it!

@daniel-hiller commented on GitHub (Jul 23, 2024): Because nobody closed it!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#39