Add extra infomation to cards

[smolBlackCat]

The current "Progress" increment only allows the users to create plain cards. For most task, this is not enough. Thus, the user should be able to add extra information to a card

• A description about the task
• A list of sub-tasks which should include the extra tasks needed to be completed before the main task.

These features should support the already existent features, like drag-and-drop, by being able to extract sub-tasks of card onto the card's card list.

The card's widget UI may change drastically after implementing this change. Also, the core library will also have to provide support for these changes by having new fields.

[Also-Spineless]

I like your software, but its features are a little weak. Some basic card data would be awesome. Each card should have a number of cells such as Title, Description, Assigned to, estimated man hours, and estimated material cost.

In version 1.6.0, the LIST provides a one-line "card". I would like to add the above information to the "card". To do this, I have to add spaces so as to get the text to appear in the next line. It would be great to be able to add a comma, semicolon or some other divider that would cause the text to go to the next line.
I added a screenshot to show what I mean.

Also, when I add spaces to create this effect, sometimes a word will appear on the next line. there is only 1 space between the colon and the word chris, but chris is on the next line.

[smolBlackCat]

@Also-Spineless
Cool that you mentioned that. I've been seeking some feedback about the current state of this feature.

Here's how it is looking for now. The video below is the current workflow added to Progress. Here the user can add sub-tasks to a card along with some notes about a certain card.

progress-demo.mp4

Although it looks enough to me, I think this could be better somehow. If you have any ideas, please let me know

[Also-Spineless]

Wow, this video shows a significant improvement for the next version.

I like the notes section for each card. That is important from a troubleshooting or progress recording point of view.

The checklist is a nice feature and is different from other Kanban systems. :)

Some new ideas

1. A card description is essential to know the task's details and what is considered finished. Often, I will have a task that needs a very specific outcome. The description will allow me to define this before I start the work.

2. The notes describe what you learned or did while doing the task. This helps explain why the intended solution(Card Description) is impossible, difficult, or an alternative is better.

3. An assignment cell is important because I might be unable to do the task. I need to describe who might do it or what skills that person has, or maybe I use crowd-sourcing.

4. Man hours describe how much time I expect the work to take. This is important as sometimes the work has a deadline, is effort-constrained or has a cost of labour.

5. At the board level, it would be nice to know the Total man-hours and cost for the number of tasks the cards describe.

6. The ability to write a formatted paragraph in the cell is very important. I want to organize my thoughts as I have done in this email. The whole section of "Some New Ideas" is an excellent example of a card description, and each numbered item would be added to your checklist with the underlined text as the descriptor.

Example

Consider another example where I need someone to translate a technical document into another language. The card would describe where the original document is, what language(s) the documents need to be translated into, Who can do it and their quote.
Cheers, Spineless
or.

It can describe a crowd-sourcing platform such as Freelancer, where I ask someone to do this work for me. I can assign it to a "future translator" later; when I find someone, I can change that to John Smith, who has agreed to do the work.

If I have a number of these tasks with different quotes/people, I would like to know the total cost and time to complete them at the board level.

Cheers,

Spineless

[smolBlackCat]

Cards have received an UI improvement over the old design

The deadline option is still a work in progress though. I managed to figure out Datetime representation and localisation. For now I just neeed to add a way of the user setting a deadline for a card

[Also-Spineless]

I like your progress. I am not sure what features from my list you have implemented. (It is your code, there is no pressure from me, I am only requesting features). However, from what I can see the UI is better. Does it have a new line feature implemented? Can you write a list without too much difficulty? Are you there yet?

As far as a deadline is concerned there are a couple of views on what a deadline actually is. ( You might already know this, but I will assume I am being helpful.)

1. A deadline is an absolute point in time the task must be completed before, such as a grant application date.
2. A target deadline, which is more like a goal that you "hope" to achieve. If you miss it by a day or two...no big deal.
3. A deadline could also be dependent on another task , or other tasks are dependent on the task described, where it must being completed on time.

These are the basic ideas of deadline. It is often related to the critical path, which is a series of tasks that represent the longest period of time to complete the project.

This is the theory.

From a scrum point of view, a "feature" has levels of perfection. The "feature" or task can have several versions. Each new version is a little bit better than the last version.

So, the best way to define a feature, such as "deadline" is to make the most simple deadline field possible. This could be as simple as a text box. later change it to a date field, later add an alarm, dependencies, and critical path information.

I don't need anything complicated. just a simple text box is fine.

Hope this helps,