Move Cards between Boards

digitalfondue / lavagna

Lavagna: issue tracker/project management tool

http://lavagna.io

GNU General Public License v3.0

636 stars 110 forks source link

Move Cards between Boards #89

Open Lysander opened 6 years ago

Lysander commented 6 years ago

Imho it could be usefull to enable the movement of cards between (backlogs only?) different boards! This way you can better model a typical sprint based development process:

For each sprint you create a new board
after a sprint's end, you "close" a board (simply don't touch it anymore)
You take all the remaining, unsolved cards from the last, finished sprint and move them to the backlog of the new sprint.

The last piece is missing right now! (Ok, you can achieve this by manipulating the database - but that's not feasible in the long sight!)

It would imho be nice, if this could be implemented.

Shouldn't be so hard, if I have understood the data model right.

The best thing would of course be a global project backlog, where you can create cards, move them to boards (for a sprint) and move them back, if they hadn't been closed during a sprint.

Of course perhaps I haven't really understood the sense of having multiple boards per project?

syjer commented 6 years ago

hi @Lysander , yes, you are right, it's a missing feature that we will implement. It's not exactly a trivial change as we will need to keep track of the previous location.

SitoCH commented 6 years ago

Hi, thank you for your suggestion. The underlining idea of multiple boards per project is to split different unrelated areas of the same project so moving a card between them wasn't planned. Moving a card can be a bit tricky because it changes the ID (OLDBOARD-1 may become NEWBOARD-3) and this will break existing links. Having said that we already have done the groundwork for it because it's surely an useful feature but we didn't have the time to fully implement it. As a workaround you can "clone" a card to another board and then delete it from the original board, it isn't really fast or intuitive but it works...

Lysander commented 6 years ago

The underlining idea of multiple boards per project is to split different unrelated areas of the same project so moving a card between them wasn't planned

Can you explain for what reason mupltiple boards are usefull? What's the reason for them you had in mind?

As a workaround you can "clone" a card to another board and then delete it from the original board, it isn't really fast or intuitive but it works...

Thank you for this proposal! Sounds good enough to deal with the situation 👍 I will give it a try!

SitoCH commented 6 years ago

Can you explain for what reason mupltiple boards are usefull? What's the reason for them you had in mind?

Sometimes you wish to split a project in smaller sizes but still keep everything unified with the same labels, milestones, reports, ... As an example we have a real world case where a single project uses one board to keep track of the actual development, another one to handle bugs and change requests for the current version and a third one to handle business request coming from "outside" the IT. You can handle everything with a single board but since these three areas are owned by different people it's easier to split everything and track the "global" progress using the milestones. It really all comes down to how you want to manage your workload...