I suggest you ...

make it possible to use categorys as columns

Many people have come up with suggestions on getting custom columns.
I have once before asked for a "status" column, and gotten a fair answer (Too many columns in total)
I was now thinking - if you could create a category, with subcategorys, and you use that as a column. Then you could create all the custom columns you'd need?

If you need any further explanaition, I will be happy to explain :)

7 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Kris Hansen shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

4 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • AdminAaron Wolf (Admin, Task Coach) commented  ·   ·  Flag as inappropriate

    Another thought:
    What about making a single "category columns" object that the .ini knows about? It would be a single column that itself actually can have multiple subcolumns so to speak.
    Then the .tsk file can specify which subcolumns are shown within this special composite column.

    Only real downside (aside from whether this is too hard to implement) is that it wouldn't be flexible for breaking up the subcolumns after the drag/drop column request is implemented…

  • Kris Hansen commented  ·   ·  Flag as inappropriate

    Example:
    [My category1]
    fixedvalue = False
    title = My category 1
    values = ["Value1"; "Value2"; "Value3"]

    [My category2]
    fixedvalue = True
    title = My category 2
    values = [%calculation_variable%]

    Forgive me for any syntax errors

  • Kris Hansen commented  ·   ·  Flag as inappropriate

    I don't know how mouch work this would require, but what if you created a copy of the column view, named it columns, and only used the "categorys" in there? You would then have to have some categorys by default (The ones we have now) and then users could create custom categorys that way?
    Some "category" columns would have to be fixed though, like calculated fields.

    This way, you can store the "category" columns in the TC.ini file, as a seperate block.

    I hope you see where I'm going here.

    Doing this should satisfy all the posts about custom fields as far as I can think of.

  • AdminFrank Niessink (Admin, Task Coach) commented  ·   ·  Flag as inappropriate

    Actually, I have been thinking about this too. If a category has subcategories, then Task Coach should allow you to add a column with the subject of the parent category as column header and the children as values.

    What makes this a bit more difficult than simply adding a column is that the available columns depend on the available categories. Right now, the columns are static and don't depend on the contents of the task file. Which columns are visible is saved in the TaskCoach.ini file. Where do we save which 'category' columns are visible? The ini file knows nothing about categories, but the task file knows nothing about columns...

Feedback and Knowledge Base