An even easier solution would be to enhance the "move card" dialog with a checkbox to copy.

So, change the "move card" option to "move/copy card" and then have an option to copy instead of move when choosing the target location.

I can do this after #1777 is merged

@jakobroehrl I'm in a great need of this feature, and lack of knoweledge of how to do that. If you would like to review your interest in implementing this feature I would greatly appreciate that.

Well, if anyone is interested in coding this, that would be awesome. I could send some euro or crypto as thank you.

Hey there! I am also very interested in this function. I have created a card as a template, which provides a checklist, as well as a Markdown formatted skeleton for the history per card.
If I could just clone instead of copy'n'paste, that would be very helpful.

Hey guys, first off, thanks for all the great work! Is there a way to contribute to the feature? I am not a programmer, but I could offer to create syntax in form of a wireframe.

If no help from a noob is needed, maybe there is a chance to know where this feature stands in terms of priority?

Useful features in terms of UI would be e.g. alt+drag on a card to create the duplicate, and the ubiquitous ctrl+C / Ctrl+V for copy and pasting stuff. I am new to the github community, so if I am smehow overstepping let me know :)

I am currently working on this. The „move card“ card menu item will change to „copy/move card“ and the dialog will contain an additional „move card“ button.

This issue was opened in 2020 and it is now 2023. The ability to copy a card is crucial. Without it we can't invest in building cards when all of the info contained in the carefully crafted cards has to be manually copied to a new card every single time. It is impossible to create cards as templates that can be quickly duplicated in mass which is the very reason for using a kanban system in the first place. How is this not no. 1 priority? How is it 3 years later and this doesn't exist yet? Kanban is impossible to use without this feature.

We use in our company a version from weeman1337 with the clone- and copy-feature (and with categories for the boards). Both works very well. Our users are very happy with this, because copying contents of cards with the clipboard is very bad. We tried to push the categories feature, but the discussion about the was more expensive than the development....

Will the Weeman version then also end up in the App Store or be merged with the actual Deck app?

I will prepare a pull request soon

Is there already something new on this issue we need the function urgently as well :)

As a feature enhancement, it would also make sense to have the option of adding a short description text to a board. Just as with group conferences in the Talk App. This would make it easier to communicate the purpose of a shared board.

Has this come any further? This feature is crucially needed. Copying cards with Checklists for repetitive tasks on different subjects is really getting on my nerves. Can anything be done to help?

As Trello changed their policies we are looking for something equal. The only thing missing and crucial for us is so far to be able to copy lists and cards. Isn't there any solution? Maybe this change of policies in Trello will push the development further...

Currently, the only workaround I know of is to create a TEMPLATE CARD that is filled out with all of the necessary data. Then, a new card would be created and the contents of the TEMPLATE would have to be copied over into the new card. It is how I do my new cards. :\

... as a matter of fact, I gave up on this one.
I removed deck from my nextcloud and chose to implement a separate wekan server in my environment.
It has everything that I need (and more...)
In my humble opinion, this task is taking too long - it's been nearly four years now.

@viceldan
I think most good projects either lack developers who want to get involved or lack the seriousness to continue the project quickly. Nextcloud itself probably doesn't have the capacity and has to prioritise. There are several similar examples with Nextcloud apps. I had another similar experience with the "Approvals" app. Thanks for the tip about Wekan

Yes 4 years an still not having such a basic and easy to implement feature is really too much.
I think the main problem in Open Source Projects is that the progammers get payed for what they do.
This would help them to spend more time on Open Source Projects.

So we should create a system, where people can ask for a feature.
The programmers then make a guess of how much work it would cost them.
Then they say we need e.g. we need 500$ to get this done.

Then people can donate for exactly this feature until the 500$ are reached.
Then they can begin to implement to get this done.
If there are 500 users and all of them donate 1$ the new feature is payed.
But sometimes people/companies would be willing to pay the whole feature alone so that it goes faster by a payement of 500$

What do you all think about that?

How much does the dev wants to me paid for this minor upgrade?

How much does the dev wants to me paid for this minor upgrade?

I would help sponsor this feature.

AND whatever you do, do not half ass this function!

When you finally get around to implementing the duplication of a card make sure that there is the option to "mirror" it!

Yes, mirror it.

That means that one card can be mirror/synced in one deck and another.

It is a complete mess for the user when they are forced to manually update all of the data in a card that is duplicated in various decks. The user makes a change in one deck and then they have to go find that same card in another deck and another and make sure the data is all the same.

No. Do not put the users through that.

This is 2023 guys. The basics here.

Create new hard linked card or symbolic linked card #6083