Best Of

Currently, Card View's Levels display options allow us to show Level 1/2/3 and below, which is really helpful. It would be fantastic to also have an option to display Level 1/2/3 and above, or Level 1/2/3 only. This addition would make it much easier for us to quickly provide a high-level overview of any given portfolio, without needing to create a Level helper column for filtering.

Thank you for considering this suggestion!

Hi.

Many development companies that use Javascript as a backend language use Typescript to increase the readability of their code.

It would be very useful if the Javascript SDK had support for Typescript so that those of us who want to use this Javascript supplement can take advantage of all its benefits.

Right now if I work with Typescript I am forced to make API calls without using the SDK.

Thanks

In Card View you can see the children elements in each card, as you can see in the bellow image.

This information is missing in the cards of the Board View and is very usefull.

Hi.

In Card View you can see the parent element in each card, as you can see in the bellow image.

This information is missing in the cards of the Board View and is very usefull.

In Card View we can view cards of the Level 1, 2, etc instead in Board View we can't. This feature is very useful because we can save in the same Sheet Projects and Task each of them has, for example, diferente status.

Hello.

One of the reasons why applying the Kanban Framework requires less team management time is because it establishes explicit policies on how to work and, above all, what a task must accomplish in order to change status.

For this reason, it would be necessary to have a space where to write a description in each state in order to indicate these explicit policies.

Furthermore, this description should be visible from the Board View and Card View to facilitate its consultation during task management.

Hello.

In order to make a proper management following the Kanban Framework it is necessary to distinguish, for each state, which jobs are under development and which, in that state, are finished waiting to be moved to the next state.

This is the way the Framework helps to change from a push management, where each team sends work to the next without knowing its capacity (and therefore generating bottlenecks, bottlenecks and bottlenecks) to a pull management where each team manages its own capacity allowing to find the bottlenecks in order to address them and thus improve the performance of the entire flow.

Thus, the proposal is that each state in the dashboard can have a ‘Doing’ and a ‘Done’ sub-column. Jobs that are in progress will be in ‘Doing’ and those that are finished for that state will be moved to the ‘Done’ sub-column.

Hi.

The Kanban framework needs the limitation of WIP in order to be applied so that teams can achieve amazing results.

The WIP limit sets the maximum number of cards a Column or Lane can have. This is how the workflow is managed.

There are 2 ways to implement it, the first one is that if the limit has already been reached, it does not allow to add another card. The second is that if the limit is exceeded, the column is marked with an eye-catching background or in some other way to indicate that the limit has been exceeded.

It would be the same for the lanes.

Also, if a column is subdivided into ‘Doing’ and ‘Done’, ideally the WIP limit should be at the global column level and affect all the cards between the 2 sub-columns.