Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limit Number of Subtasks Shown Option #16

Open
darthmachina opened this issue Oct 31, 2021 · 7 comments
Open

Limit Number of Subtasks Shown Option #16

darthmachina opened this issue Oct 31, 2021 · 7 comments
Labels
kind/feature New feature or request lifecycle/idea Needs more thought/information/consideration/mulling over triage/confirmed Understood: should have a lifecycle label assigned.

Comments

@darthmachina
Copy link
Contributor

I tend to break down my tasks to a fairly granular level, which means my subtask list can get pretty long. It would be nice to have the option to limit the number of subtasks shown on a card. If there is a limit set I would show the first n items in the subtask list with a line that indicates how many more there are.

It would be nice to have this be a configurable option to set the amount of items to limit to. Setting this to 0 could indicate that there is no limit which would mimic the current functionality.

Something like this, if the limit was set to 2:
image

@roovo roovo self-assigned this Oct 31, 2021
@roovo roovo added the kind/feature New feature or request label Oct 31, 2021
@roovo roovo added this to the Post Initial Release milestone Oct 31, 2021
@roovo
Copy link
Owner

roovo commented Oct 31, 2021

Great idea and should be pretty simple to do - so will add it to the next milestone :)

@roovo
Copy link
Owner

roovo commented Nov 3, 2021

A couple of things have now come to mind (applies to #17 too):

  • I would make this a global configuration as I want to keep the board configuration options as small as possible. Would this line up with your use case?
  • (sort of) in line of the tooltip discussion -> is leaving this as it is a way of forcing people to break down their task lists a bit more so they don't end up with one with a big pile of subtasks. And would this be a good thing? It could help give people a sense of flow when dealing with tasks as they would be getting more cards done.

@roovo
Copy link
Owner

roovo commented Nov 3, 2021

I am going to move these out of this milestone for now as more thought required!

@roovo roovo removed this from the Post Initial Release milestone Nov 3, 2021
@darthmachina
Copy link
Contributor Author

I spent a little time looking at this last night, and I agree that making it a global configuration. At least, I would want it to be the same across all the boards. Same with #17.

As for the second point, I can see your point but I do think it's different. I like my cards to be a single completable thing but when breaking it down the steps it can still get pretty big. I have ADHD so I tend to go pretty granular so I don't forget things later. Some of the cards related to things I'm working on for work can get to 25+ subtasks, especially since I'm dealing with multiple related code repositories. The option to hide completed tasks is probably more important than this one, at least for my workflow, but I think this one is still valuable.

@roovo
Copy link
Owner

roovo commented Nov 3, 2021

I'm coming round, but will leave it where it is for now as there is plenty to be doing!

@darthmachina
Copy link
Contributor Author

I hear you. Like I said, #17 is probably the more important of the two, at least for me. I do have some cards where viewing the whole list is nice, but removing completed subtasks cleans up the board as well but leaves undone things still visible.

@roovo roovo added this to the 0.3.0 milestone Nov 7, 2021
@roovo roovo removed their assignment Nov 7, 2021
@roovo roovo added this to Next Release in CardBoard Dev Nov 9, 2021
@roovo roovo moved this from Next Release to To do in CardBoard Dev Nov 12, 2021
@darthmachina darthmachina moved this from This Release to In progress in CardBoard Dev Nov 16, 2021
@darthmachina darthmachina self-assigned this Nov 16, 2021
@darthmachina darthmachina moved this from In progress to This Release in CardBoard Dev Nov 17, 2021
@darthmachina darthmachina moved this from This Release to Review in progress in CardBoard Dev Nov 17, 2021
@roovo roovo modified the milestones: 0.3.0, 0.4.0 Dec 23, 2021
@roovo roovo removed this from Review in progress in CardBoard Dev Oct 1, 2022
@roovo roovo removed this from the 0.4.0 milestone Oct 2, 2022
@roovo roovo changed the title [Feature Request] Add Option to Limit Number of Subtasks Shown Option to Limit Number of Subtasks Shown Nov 30, 2022
@roovo roovo changed the title Option to Limit Number of Subtasks Shown Limit Number of Subtasks Shown Option Nov 30, 2022
@roovo
Copy link
Owner

roovo commented Dec 2, 2022

Need to think about how this would work if this task is appearing on a board because of the tag on a sub-task. If that sub-task is hidden due to this limit then this could be confusing as it would not be obvious why it was on a board when looking at the card....

See #95 and #83

@roovo roovo added triage/thinking Needs more info/thought/consideration before prioritizing and removed needs-triage labels Dec 28, 2022
@roovo roovo added triage/confirmed Understood: should have a lifecycle label assigned. lifecycle/idea Needs more thought/information/consideration/mulling over and removed triage/thinking Needs more info/thought/consideration before prioritizing labels Jan 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request lifecycle/idea Needs more thought/information/consideration/mulling over triage/confirmed Understood: should have a lifecycle label assigned.
Projects
Status: No status
Development

No branches or pull requests

2 participants