A couple questions about CWM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- Is there an ability to add a colored dot/tag like in VTB to a card? If not what would be an alternative?
- When viewing the kanban board what is the alternative to the VTB being able to click on a user's name at the top to automatically filter by what's assigned to that user?
- Will raw HTML tags always show in the Kanban board inside a card?
- Does anyone have issues collapsing the horizontal swim lanes in kanban view?
- When going through a backlog, does anyone else realize the filter doesn't persist and resets going to the next page?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi Marlon,
"if no Sprint is assigned to those Draft stories in the Backlog then they shouldn't be shown in the Kanban view." - We completely understand the requirement here. in H1 2026, we will have kanban filters which solve this problem.
"Also I want to be able to hide a vertical lane." - this is not possible at the moment. Nevertheless, we will consider this for future roadmap.
"what is the best practice of importing old Sprints from VTB into CWM so that the previous Sprint of the story when importing the Story into CWM remains instead of blanking the Sprint field out?"
We don't have out of the box capability to migrate at the moment. Best approach is if you want to do this for all teams in the organisation - it will be better if you do via background scheduled job which would create equivalent space per team, active and future sprints.
if you have EAP (Enterprise Agile Planning), the path will be different. We can guide you better with our Product Management based on the current setup you have in the organisation.
Would you be able to raise case with us to take it further?
Thanks and regards,
Sunil B N
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
I would definitely like the roadmap on how to do this with EAP implemented
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
I'm being told that this is working as per design:
- Connect tables to board using Connected Work
- Click Sprint Planning tab
- Click "Manage filters" button to select which work item types to be shown in the backlog
- Click the filter icon on the State column in the Backlog section
- See all states for all work items added from Connected work
- Despite clicking the Manage filters button in the Backlog section to select specific work items to only be shown, ALL states for ALL work items connected via Connected work is shown even though only Story was selected
- This means if a user connects Problems, Requests, Incidents, and Changes then the States for all 4 tables + Story states are shown in the filter even though a user selected to only show Stories in the Manage filters section of the Backlog
- Despite clicking the Manage filters button in the Backlog section to select specific work items to only be shown, ALL states for ALL work items connected via Connected work is shown even though only Story was selected
When using Connected work it's "Working as per design" to ignore the filters set in the Backlog for work item types to be shown and display all the states for all work items connected via Connected work? How is this acceptable design from a usability standpoint?
If I only select stories in the backlog, but have connected incident, requests, problems, and changes then I should only see the states for stories. Not the states for work item types I DID NOT select to be shown in the backlog.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Friday
Hi Marlon,
If I understand it correctly, you are filtering "Task type" in backlog list view to see only stories.
And the expectation is that state column choices should only show story's states and not all the task types. We understand the pain point here for this use case.
Imagine if they have selected two types and filtered using some states of both types, then if user unselects a type, we would have to remove some filtered states. - this is when it can get messy.
Please note that these filters are UI filters for quick filtering and there is definitely room to improve the choices we show in state/priority (as we combine all values into one). We will definitely consider this feedback for further improvements for filtering feature.
Thanks and Regards,
Sunil B N
