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

Make the first column (aka. untriaged) to consider the provided Milestone in the filter #273

Closed
haikalpribadi opened this issue Sep 23, 2018 · 2 comments

Comments

@haikalpribadi
Copy link

@haikalpribadi haikalpribadi commented Sep 23, 2018

At the moment, the first column ignores the milestone provided in the filter.

This makes it very confusing and misleading to use the board view of the filter. Take a simple example: we want to build a kanban board for a given milestone, say v1.5. So we make filter with to settings: view=board, and milestone=v1.5. However, when we go to the filter "Milestone v1.5 board", we see all the open/untriaged issues in the first column. This makes it very difficult for us to scope our work.

Is it possible for you to do a simple toggle in the project setting for "filter untriaged with Milestone"? Envisioning the code that goes into this, this should be fairly simple to implement and shouldn't break anyone's workflow.

@kareem
Copy link

@kareem kareem commented Sep 23, 2018

Hey @haikalpribadi can you help me understand a little more why this is painful for you? Is the issue that the column is there at all? Because if so you can hide it by toggling it to hidden at the bottom of the page:

unified - board 2018-09-23 14-36-47

@haikalpribadi
Copy link
Author

@haikalpribadi haikalpribadi commented Sep 23, 2018

Hi @kareem,

We need the open/untriaged/first column in the board, to know what are the open issues in that milestone. Thus, if we hide the first column, it doesn't become a solution for us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants