Possibility to change the order of custom fields in card view
marked this post as
Hans Dahlström: 🎉
If all goes well this will be released on Sunday
Hans Dahlström: YAS! Very exciting. Thanks for the update Hans.
marked this post as
work on this has started
Merged in a post:
Hide or collapse standard/custom fields in card view
When using custom fields extensively, these together with the standard fields use up a very big portion of the screen of a card.
It would be great to have the option to collapse or hide the complete fields section to only view the title and the description of the card in the card view.
It appears that this is pretty much a duplication to https://favro.canny.io/feature-requests/p/possibility-to-change-the-order-of-custom-fields-in-card-view
Simon Kranz: Thanks Simon, I will merge this, as we are already in plan to implement this.
Question to community. One idea we have is that custom fields can be grouped.
* This custom fields grouping is centrally managed by administrators
* The group can be collapsed or expanded by users individually.
* The order of groups and fields can be changed by the board owner on each board individually, but he order within the group is preserved and cannot be changed.
Like or dont like?
Jan Van Lysebettens
Hans Dahlström: I don't like it. Makes it overly complex. Just having control over which properties are shown ( thus removing silly defaults like tags & timeline ) and the order in which they are shown would already be a huge, yet simple, step forward.
Hans Dahlström: I love it!
Hans Dahlström: I am not an admin but the owner of multiple boards for a big team. No admin would be able to group our custom fields effectively. Limiting this ability to admins only would not solve anything for us.
I do like the grouping feature though - hence the 'like' under your comment.
Hans Dahlström: Thanks, Hans! This would definitely be an improvement, but it feels like an intermediate step toward the more customer-focused solution of allowing us to order card fields as needed, regardless of core/custom type.
Merged in a post:
Collapse custom fields
Once the number of custom fields grow above 7-10, the description of a card disappears below the fold, meaning you have to scroll down to get there.
We work in a process where a number of stake holders track various initiatives in a sheet with multiple columns for custom fields like priority, next steps, health, etc. When we want to drill down and see the details of a card we click on it to open, but the only thing we see directly are all the custom fields which is exactly what was shown on the sheet before the click.
Having a collapsed version of the fields would be good, and in our case it would have to be a universal toggle, like when you shift between dependencies and relationships.
We think this is a good idea, however it can render inconsistent views across boards because cards can exists in multiple places. Here are some scenarios on who can change the order and which consequence this will have. Any thoughts on this?
* Only admins can reorder fields and it will update on all boards
Highly centralised model and little decentralised ownership (which is Favro's model)
* Board owners can reorder fields and it will update on all boards the card is on
Boards will look mostly consistent but will changes ripple through (for other cards on other boards?)
* Board owners can reorder fields and it will update on boards the owner has access to
Boards will look mostly inconsistent but will changes ripple through (for other cards on other boards?)
* Board owners can reorder fields but it will only update on local board and will look different on different boards
All boards will look inconsistent because fields can be in order on one board, another order on another board, for the same card.
Hans Dahlström: My vote would be on "Only admins can do it and it will update on all boards". The whole reason I'm voting on this feature in the first place is to make the views consistent.
Juliane Bogenschütz: Thanks
Mattias Björkholm Alexi Jesse Boyarski Derek Shirk - any thoughts on above?
Hans Dahlström: I’d love the ability for board owners to be able to be able to reorder fields as they please and it will automatically update the same card on other boards.
Having only admins being able to change works too but it quickly creates bottlenecks. I’d love to allow teams to do that themselves in boards they create.
Alexi: Thanks - how do you think about that boards will have different order of fields? is it ok or will it create a bit of a mess?
Hans Dahlström: Ability for admins to update across all boards would be a good start. Our organization has different types of engineering teams and each team has information that may be more important to see first for their workflow. We could probably standardize this, but it may be nice to have the flexibility to have board owners update the field order for cards on their boards specifically.
Hans Dahlström: As Juliane Bogenschütz said. The reasoning behind the reordering was to achieve a more consistent look.
Hans Dahlström: I'll gather my thoughts and reply as soon as possible.
Hans Dahlström: For my team in most cases, it will be okay. The team would be looking at their own respective boards anyway. I would love to have the ability for the team to customize their view to fit with how they perceive information.
The reason why I think it is okay and won't be a mess is that people can create their own board with their own views and I think that's what makes Favro so unique. We can customize the order of custom fields and only show relevant info pertaining to certain groups which I think is awesome. The issue I remember with JIRA is that so many people want different fields on the same card so you end up with just a massive list of custom fields but really, only a few custom fields are relevant to you.
That said, I could see a consistent view across all boards would be extremely important for things like bugs. This helps to make sure that everyone is looking at and triaging the same information across the board.
Perhaps an option to do both? Is it possible to lock fields? Certain fields you cannot move (unless you're an admin) and certain fields you can? Options to also hide fields that are not relevant?
Would also be great if in the card details, we can have tabs for group of fields like in JIRA.
I showed up here today to create a feature request for this very thing. Thank you for adding this, and thanks to everyone who has upvoted it.