-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clone / Copy boards [$150] #119
Comments
Makes sense. Would also be nice to have for cards/stacks as well. |
This comment has been minimized.
This comment has been minimized.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I would like to extend the template idea for boards from #154 to stacks. Atm we are using one board for the planning of a recurring event, where the tasks are always the same. One stack corresponds to an event at a specific date and the first stack serves as a template.
If this option existed one would not have to hack the database each time to copy stacks manually ;) |
We have the same case, similar rutines and way too many tags to write them every time. I don't know if that was discussed already, but it would be also great to have a new tag automatically added to the board when someone writes that in the blank tag field. Anyway, great app! |
We make much use of templates in Kanban boards. If you create a new board, you don't want to design it again an again. |
We use nextcloud in our cooperative. We would like to say goodbye to Trello and change completely on deck. But the function to copy boards is missing. We would welcome this extension and are willing to pay an amount of CHF 150. Thank you for your efforts so far! |
Duplicating boards (and stacks and tasks) seems to be a really crucial feature in order for Deck to be really useful for any medium sized project management. |
@Energiegenossenschaft You can always put a bounty on it at https://www.bountysource.com/issues/44830048-clone-copy-boards That way community contributors who solve the issue will get the money then. |
This feature is absolutely needed. Add templates or Copy or both, and it will become a web based project management solution overnight. I'm an architect licensed in two states who plans to use this system for collaborative project management - one-stop-shop. |
It is practical if a project template can be created and cloned with the whole content. The cards should be included, otherwise the whole thing doesn't make much sense! |
THe point for not including them would be that I was assuming that a template would define the board layout (columns) and labels, while the actual cards or tasks would be different for each new clone of the board. But maybe we can just add an option then to either include cards or not when cloning. |
This would be ideal, to choose by cloning the board with or without the cards. We would very much welcome an implementation and integration in the coming weeks. We would be ready to pay additional CHF 100 for this. Do you think an implementation by mid of June is realistic? |
I won't have time for this, but maybe something for you to implement and hunt some bounty @jakobroehrl since you already did the first part of cloning. 😉 |
Will do this, after #1777 is implemented |
Hey there, I'd just like to let you know that due to the ongoing issue with Bountysource we're discussing ways to move to a different platform. As it looks right now, Bountysource might claim some of the money that was contributed by the community. We will try our best to prevent that. Historically we – the Nextcloud GmbH employees – simply put the claimed bounties back to other tickets until one was solved by a community member. So the money was always from the community and for the community. We'll therefore move to a better platform and currently don't post any new bounties until this situation is resolved. The current goal is to move/donate the money to Nextcloud include but details will follow in the forum post. Hope this makes sense. If you have any questions please ask them on the forum. This comment will be copy-pasted to all open issues with bounties. |
Received a request today that the clone function doesn't include the cards, so it looks like at least some users expect them to get copied, too. |
Indeed I expected at least the option to duplicate a board with all the cards to have a "template-board" for same type of projects. |
Is there any eta on cloning of the cards along with the boards? I'm trying to implement a template type system since our work process is largely the same for each project, and was surprised to find that "Cloning" the board didn't automatically clone the cards as well. Thanks. |
This could be implemented quite easily with https://github.com/maxammann/trello-to-deck/issues Would this be sufficient for the people who have the need to clone boards? |
Totally necessary. All other pro board software has this. Trello included. Opensource Wekan also has it. Templates are a required feature for businesses because they define for a specific purpose and need that same purpose over and over again. Copying a board might work as a substitute but it's a hack compared to the right way which is defining multiple templates, allowing to name for their intended purpose and then use them as needed. Love the direction Deck is headed but this should be on the short list in my opinion. |
Our cooperative uses deck every day and we are very grateful for this tool!! Cloning boards, including cards, would make our day-to-day project work , we are building solar powerplants, much easier. Of course, we would still pay the promised commission of $300. |
@juliushaertl |
Closing in favor of #2797 for the remaining part to also clone the cards. |
Imho it would be very helpful to be able to copy boards with and without their content
So you don't have to create the Markers new for each board and can split boards monthly or weekly
Btw: Thanks for your great work!
There is a $150 open bounty on this issue. Add to the bounty at Bountysource.
The text was updated successfully, but these errors were encountered: