Custom fields for tasks

Feature Discussion
1

It would be really nice to have some custom fields.
Maybe Labels could address some of this, but I don’t think all use cases, otherwise the label list becomes long and unwieldy.
Labels are a great but they’re pretty clumsy for managing many categorisation needs.

2

I think that could be a good use case for a plugin (once we have a plugin api).

What use-case do you have that cannot really be solved with labels?

3

I’m thinking some attribute of the task.
It would likely change according to the namespace

So a task in a list in a namespace for Servers might need custom fields for RAM_Size, Disk_size, Host_platform

Whereas a task ina lis in a namespace for domains might need custom fields of registrar, dns_provider, client

With 4 x ram_size, 4 x disk_size, 4 x platform, 4 x registrar, 4 x dns_provider, 20 x client, you would have 40 labels. And it would only grow from there. 40 labels is a lot to manage, even with some colour-coding.

Side note : the text on a colored lable is not easy for me to read. Is there a way to increase font size ?

Anyway, maybe you have different way in mind to manage that kind of use case.
And sorry if I am missing the obvious in how to use the app for that.

1 Like
4

Thanks for the clarification. I think that’s a good use case.

5

Hi I also think this would be a great addition, especially if you could see those fields in the list view and also sort by those fields. Maybe similar to the way ClickUp does it?

8

Hi @kolaente,

I just wanted to confirm—custom fields for tasks are still not implemented, right?

I’m considering taking a look at this feature. It would be helpful to have a PR or commit that introduces a new field to the task details schema and also integrates it into the UI components.

For example, let’s say there was a feature request titled “Add Priority Field”, and a specific PR was linked to it. If such a change exists, I could review it to understand:

  • Which areas of the codebase were affected
  • How schema changes were handled
  • How the UI was updated accordingly

This would give me a starting point for incorporating custom fields logic in a similar way.

Is there any commit, PR, or high-level feature you could suggest as a reference?

9

yep.

I think all of the current fields were added without PRs. I can’t really check it because the search is broken on Gitea :confused:

There is some documentation about the schema changes work and how to develop features in the docs: Development

1 Like