The new GitHub Issues – February 23rd update

Today, we are sharing new updates to our projects (Beta) experience, including some highly requested filtering additions and more on our continued investments into project insights.

👉 New filter syntax

With more filter flexibility, you'll have several new ways to work with filters in your projects, including:

• Assignee:@me – use our new @me filter alongside the assignee field to show items assigned to you.
• Iterations @next and @previous – easily filter to the next or previous iteration as enhancements to the existing iterations filter @current.
• Number and date type fields now support all existing GitHub search syntax – including >, >=, <, <=, n..*, *..n and n..n.

🏝 Iteration breaks

In our last update we made iterations more flexible with adjustable dates and lengths. We've built on that by adding in breaks making it easy to communicate when you and your team are taking time out from their iterations.

📈 Persistent charts

The insights alpha continues to improve based on your feedback. Previously we introduced chart filters, helping you get to the insights you care about. With the addition of persistent charts, you can now save and name these filtered charts to share with your team – just like you can with views.

Join the discussion to share your feedback and experience with the insights alpha.

✨ Bug fixes & improvements

Other changes include:

• When editing a project description or README, the cursor will default to the end of the text rather than the start.
• Bug fix where adding a second filter after a comma would replace the original filter.
• An or filter can now be created when using the iterations @current option. For example: Iteration:@current,iteration-10 will correctly return all items in either the current iteration or in iteration-10.
• Bug fix where focus is lost after adding an item from the suggestion menu.

See how to use GitHub for project planning with GitHub Issues, check out what's on the roadmap, and learn more in the docs.