freelancegogl.blogg.se - Hyperplan subtasks

#Hyperplan subtasks code#

Now each such list (board) can contain 0 or more items (in Asana terms this is a section, in Libreboard terms this is a. Trelly and libreboard visualizes this same list horizontally. Asana has visualized this list as a vertical list. Here is how Asana team has implemented this feature.Įach project (in Kanban terms this is a board) is a completely independent list. In fact, the simpler you think, the easier will be to move on and make additional changes in the future. Implementation wise it is relatively simple, too. Each team can rearrange the same task in their preferred way. For the marketing team your Feature X is the top priority, for security team this task is medium. Inside those projects, the same task can be under completely different section in completely different order. In Asana terms, users can choose 0 or more projects/sections that a task can belong to. The implementation that Asana team has provided is quite neat from the UX perspective and doesn't clutter the UI.

So different people may want to choose to organize the same set of tasks/cards in different ways.

There are marketing guys who also don't care about implementation details, however they are interested in the parent/bigger tasks that their team and their next big launch depend on.

Say the CTO doesn't need to know which tasks go into your next release, however he needs to see your task/card that tells the story of you next release (you will have some just for him).

Some people need to know the overview of the things going on in the company, some need to know the details.

There are different people in the organization with different needs and views.

Have a look at how Asana can assign a single task to multiple projects and multiple sections.

#Hyperplan subtasks code#

With this feature implemented, the usual label and assignments features could potentially be removed, simplifying the code and further differentiating from Trello. It would also be nice if I could color-code the labels by assigning colors to the columns from which they are derived.) (It may be nice to be able to choose exactly which labels are shown in order to avoid clutter. So, e.g., when I'm looking at "completion state" I can also see each card's "priority" shown inside the card. Moreover, when I'm looking at one column set, the cards should show internal labels indicating the card's position is column sets I'm not currently viewing. Then, instead of setting labels or assignments, I would switch to the column set I am thinking about at the moment and push cards around. So what I want instead is to be able to define multiple column sets for the same set of cards. Dragging cards between columns is way more fun. Setting a label requires 5 precision clicks and delay time while UI elements load. Some of the others may be handled by labels or by assignments, but the UI for these is far less pleasant than dragging cards around. Right now, I can only choose one of these to be my columns.

Completion state (the usual wishes / not started / in progress / needs polish / done).

The basic problem right now is that there are several different ways in which I might want to organize my cards. I've been using Libreboard to organize the roadmap for Sandstorm.io, and I thought of what I think would be an incredibly powerful feature.