# Using issue filtering in github
**URL:** https://discourse.julialang.org/t/using-issue-filtering-in-github/1455
**Category:** Offtopic
**Created:** [January 13, 2017, 8:27am UTC](https://discourse.julialang.org/t/using-issue-filtering-in-github/1455 "2017-01-13T08:27:23Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@lobingera](https://discourse.julialang.org/u/lobingera)
#### Post date: [January 13, 2017, 8:27am UTC](https://discourse.julialang.org/t/using-issue-filtering-in-github/1455/1 "2017-01-13T08:27:23Z")
I tried to look around on the julia issues about the state of multithreading.
I can filter issues to is:open and label:multithreading but i cannot filter to the milestone.
If i go to the milestone page all issues are presented open and close, but no other filering (like recently changed etc.) can be applied.
How do i filter for open and closed issues on multithreading, being part of the 0.6.0 milestone?
---
### Author:  [@Gnimuc](https://discourse.julialang.org/u/Gnimuc)
#### Post date: [January 13, 2017, 8:38am UTC](https://discourse.julialang.org/t/using-issue-filtering-in-github/1455/2 "2017-01-13T08:38:51Z")
`is:open label:multithreading milestone:"0.5.x" ` works fine, take a look at this [filtering-issues-and-pull-requests-by-milestone](https://help.github.com/articles/filtering-issues-and-pull-requests-by-milestone/).
---
### Author:  [@lobingera](https://discourse.julialang.org/u/lobingera)
#### Post date: [January 13, 2017, 8:52am UTC](https://discourse.julialang.org/t/using-issue-filtering-in-github/1455/3 "2017-01-13T08:52:20Z")
Thank you, i wasn’t aware of the syntax. Unfortunately no many multithreading issues are assigned to 0.6
---
### Author:  [@Gnimuc](https://discourse.julialang.org/u/Gnimuc)
#### Post date: [January 13, 2017, 8:52am UTC](https://discourse.julialang.org/t/using-issue-filtering-in-github/1455/4 "2017-01-13T08:52:59Z")
you failed to filter out a multithreading issue in 0.6.0 milestone just because it doesn’t exist. you can use something like this `is:open label:multithreading updated:>=2017-01-01` to keep tracking latest issues.