1. There needs to be a way to input time into a task from the Kanban board. The way things are right now I have to browse away from the Kanban board to the task page to enter time, then return back to the Kanban board. A time input box should be available in the Kanban card when it's expanded on the...
There needs to be a way to visually associate parent tasks and their subtasks in the Kanban board. Subtasks should be placed under and indented in from their parent task, or subtasks should be seen in the parent card when the parent card is expanded.
In the WF Kanban view (unlike the Scrum swimlane...
This could be generalized to behave more like the standard task list with a Filter, Grouping and maybe even View options.The filter should cover anything filterable in the task list view. We'd like to be able to filter by assigned job roles, so that a set of UX Designers (for example) can look at j...
After breaking down our coarse grain backlog stories we end up with a nicely detailed backlog of small enough pieces to actually work on. Unfortunately, those details are lost on most except for the dev team. We need a view that shows the high-level stories only and hides all the detail. Requeste...
Given a long backlog breaking down a story is painful because it moves all the new sub-stories to the end of the backlog. Instead, I'd prefer all the sub-stories to be placed in the _same_ location where the parent was.
This avoids having to scroll to the bottom, identify the sub-stories, and then ...
We use the `Backlog > All` view to see tasks grouped by the iteration they are assigned. All items not assigned to an iteration show up in the "No Value" grouping. From this view, no matter which story you choose, the `Move to...` dialog only allows you to move the selected story to another iterat...
If the waterfall project views are still important, then WF should be configurable to override the planned completion date or not. Choosing one approach obviously doesn't work for everyone.
We use "Add More Tasks" all the time and it generally works well. If all the fields are valid, it will save as expected. If instead the start data is accidentally before the project start date, it fails validation the inline form disappears and all the data you just entered is gone -- job roles or...