I could have this use case not quite right, but it seems to me that if I create custom fields on board A, then I move a card from board A to board B, the custom fields from board A will now be applied to all cards on board B. That's not ideal. I'd like the fields to stay with the individual card as it moves from board to board, but if you have instances where cards from 5 different boards with 5 sets of custom fields could all be moved to 1 board, then that 1 board where all those cards from other boards ends up are going to have a ton of custom fields that don't make sense for those all of those cards, and the cards start to look overburdened with custom fields and are, therefore, harder to work with.
A board is not a container for issues, it is a view of a set of them, so you do not "move a card from one board to another".
Because they are a view, when you configure a board in one way, it is going to display all the issues it selects in the same way.
@Carrie CurtnerIn Trello, custom fields are defined per board. That means all cards on a board have the same custom fields. So, if you move a card to a new board, the new card's custom fields get added to the board's custom fields.
Please have a look here: https://help.trello.com/article/1067-using-the-custom-fields-power-up under the heading "Moving Cards with Custom Fields" for more information.
Thanks for the clarification, @marc. This is less than ideal for the way our team moves things from board to board, it results in, sometimes, 20+ custom fields on the board we have in which all individual team boards converge, with only a small percentage of those cards needing all fields. I can see both sides of this being good or less than good UX, and you're not going to make everyone happy, I guess.
Thanks again for the response, though. It's helpful.
I agree with @Carrie Curtner as well.
I think everyone understands how it currently operates.
However, given the way it currently operates, this confuses the direction and bloats other boards that have different purposes. If I have a "Bug" board with custom fields for its cards and then want to assign a bug over to another board, that whole board becomes comprised with all the "Bug" boards custom fields.
It makes sense for the parent/defining board to have all of its cards with every custom field defined, but the moment it moves to another board, that board shouldn't adopt all the custom fields from the originating board. (In my opinion)
Also, if they were to make a change, I can't think of way how this would be detrimental to other boards.
You could apply flag settings, for example: adopt customer fields from board "some board name" [ x ].
This is similar to how you currently create checklists.
If you had to thrive a new habit during a lockdown, what would it be? Trello
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event