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

Ability to hide "future" tasks #98

Open
mkay82 opened this issue Jun 11, 2015 · 2 comments
Open

Ability to hide "future" tasks #98

mkay82 opened this issue Jun 11, 2015 · 2 comments
Labels
feature request Request or idea for a new function

Comments

@mkay82
Copy link

mkay82 commented Jun 11, 2015

Hi,
sometimes i add to redmine tasks, which should be done in future (sometimes even few months after the date i've added it). it's just a reminder for me, bu unfortunately i see them all in dashboard...

it would be nice if dashboard has an option to hide tasks, which has start time in future

@jgraichen jgraichen added the enhancement Improvement to an existing functionality label Jun 11, 2015
@janekska
Copy link

janekska commented Jul 7, 2015

I am thinking about the same - I guess that it is a kind of icebox in agile terms.
I thought about it in a kind of different approach - it is more an issue, that has one or combination of properties:
Not assigned to any body,
Has no estimation of needed time,
Has status less then X.
If we look on first one it could be done already by changing the assignee filter. I guess that it could be also a bit logic, that "All assignees" will show all issues with assignee. Than we can use "unsigned" as icebox filter if any body will need them. But in my work for icebox search I would rather use issues list and form there put it them in the backlog/current state.
For second and third properties of icebox issue it would be good if it would be possible do not include them in dashboard at all.

@mhartung
Copy link

mhartung commented Aug 1, 2017

My approach to this idea is the wish to add any Redmine custom-field as a filter whether to show cards or not to show them.
For example we are using custom-fields that mark each ticket as "active part of the kanban board" (kanban=yes), to distinguish them from all other tickets that are just floating around collecting dust. I am aware that the categories could be used equally, just that we already use them in different ways.

@jgraichen jgraichen added feature request Request or idea for a new function and removed enhancement Improvement to an existing functionality labels Jul 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Request or idea for a new function
Projects
None yet
Development

No branches or pull requests

4 participants