The problem is simple:
- lets say I have 30 contexts
- lets say typical task has more than 5 contexts
In this scenario, showing contexts in the props line is pretty useless,
because it's too much information.
However If I could define, what contexts show up in the props line, only 1
or 2 out of
I'm not clear on what the issue is, so let me be a little more
specific about what I am proposing.
You have some contexts that are not used for filtering and that
you would like to see in the task list. Let's suppose that some
examples are @call, @email, @spreadshee
The following is besides the original point of the request.
I don't like how tags are implemented.
They are fine for putting a single tag on a task.
But the way it creates "combined" tag when putting more than one tag on a
task renders it unusable for me.
I can't even imagine what your suggest
If you used tags instead of contexts for the filtering would the
problem go away?
On 7/7/2022 05:49, Radek Pilich wrote:
Consider adding new setting to the context items - Show in props
line.
Right now, ALL assigned context appea
Consider adding new setting to the context items - Show in props line.
Right now, ALL assigned context appear in the props line, which makes the
feature of showing contexts in the props line pretty much useless if using
more than 2-3 contexts for a single task.
I use multiple context "sub-group
