The new GitHub Issues – January 13th update

New year, new GitHub Issues improvements! 🎉

We had several updates at the end of last year and are kicking off the new year with a number of improvements to the projects experience.

✅ Check in with reviewers

Many teams use reviewers to manage their pull requests, with our new field type – reviewers – any pull request added to your project will now display any assigned reviewers. Making it easy to see who’s been requested to review a pull request. To get started with reviewers:

• Open the new field menu or the command palette and add the field reviewers to any of your existing views.
• On the table this will display as a new column.
• Or on the board this will display embedded in the card.
• To keep the new field as part of your view, select save changes in the command palette or view menu.

The reviewers field is currently read only, with write access coming soon.

💙 Updated filter bar

It is now easier to see which filters have been applied to a view with our new tokenization in the filter bar, with filter criteria now displayed in blue and helpful error messages when no matches are found.

✨ Bug fixes & improvements

Other changes include:

• Assignees are now always displayed in the side-panel for draft issues.
• Bug fix for the selection behavior of multiple cards in the board layout. Previously clicking the ... menu would unselect all cards – making it hard to bulk remove multiple items.
• The close button in the draft issue side-panel can now be navigated to with the tab key.
• Bug fix so the filter -@current now includes items with no iteration – which is consistent with other negative filters.
• When a board is pivoted by a value other than status, the status value can now be displayed as metadata on the card.

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