issues

Subscribe to all “issues” posts via RSS or follow GitHub Changelog on Twitter to stay updated on everything we ship.

~ cd github-changelog
~/github-changelog|main git log main
showing all changes successfully

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.

Reviewers

💙 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.

image

✨ 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.

See more

Following our last update, we have a number of exciting updates and improvements being released today for the new projects experience.

🔗 Stay in sync with linked pull requests

One of the top requested features, you can now easily see what work is in progress with our latest field type linked pull requests for both the table and board layouts.

  • Open the new field menu or the command palette to add the field linked pull requests 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.
  • Learn more about linking issues and pull requests.

Linked pull requests

📝 Shape your draft issues

We have added multiple improvements for draft issues, you can now:

  • Add assignees ✨.
  • Include a markdown body.
  • View and edit the content in our new side-panel.

Then easily convert your draft to an issue in your chosen repository when you are ready.

Draft issues

🐇 Access your projects through your repository

To bring your projects closer to your code, you can now curate a list of projects useful to your team under the projects tab in any repository. Projects are still created and owned by the organization or user but are now much faster to access.

  • Open the projects tab in a repository.
  • Hit the add projects button to search for a project under the same organization or user account as the repository.

image

✨ Bug fixes & improvements

Other changes include:

  • Group by is now enabled for both assignees and repositories ✨.
  • Iterations have a new filter option to always return the @current iteration.
  • Bug fix – for certain Japanese characters in the omnibar.
  • The current iteration now includes the current label when in group by.
  • Date ranges for iterations are included in the board layout.
  • Bug fix – sort by assignee will now be in alphabetical order, regardless of case.

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

See more

We’re consistently expanding the capabilities of projects (boards & tables) on GitHub, and we’ve got a handful of exciting updates and improvements launching today.

💫 View your boards by any field

When you are in the board layout, you can now pick any single select or iteration field to use for columns.

  • Open the view settings menu and select column field.
  • Choose any of the available single select or iteration type fields.
  • Drag and drop your items to update your selected field.

Board Columns v3 1

✅ Set fields to items added under a filter

No more disappearing items. When you add an item to a view with a filter, those fields will now automatically be set.

Adding under filter v3

👋 See your team

With our new presence indicators we continue to evolve the real-time experience in projects, you can see who on your team is making updates to the same projects you are. Presence indicators are currently only enabled for organization owned private projects.

floating heads v2 2

✨ Bug fixes & improvements

Other changes include:

  • Clicking into the filter bar will now automatically add a space.
  • Bug fix where previous iterations would not display in the board layout.
  • Fixed an overflow issue with long view names.
  • Added the ability to filter by type, to switch between users or teams under the manage access settings page.

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

See more

After our GitHub Issues public beta announcement at GitHub Universe, we’ve seen teams start to engage with and adopt project tables, boards and all of our recently released features. Now that we’re in the public beta, we’re going to continue to ship on the same cadence we did during private beta (every 2-3 weeks), engage with your feedback, and deliver on the feature roadmap.

Here are the latest updates which are available to all projects on GitHub.

🔀 Re-orderable views

One of the most requested features in our feedback forum, you can now easily re-order views via drag and drop to get the perfect sequence.

🏈 Team permissions

The manage settings screen now supports adding permissions directly to GitHub Teams, making it even easier to ensure everyone has the right access level needed for your projects.

✨ Bug fixes & improvements

Other changes this week include:

  • Clicking outside of the board will now de-select any selected cards on the board layout.
  • Resolved a problem where archiving all cards in a column would also archive cards filtered out. Now only visible cards will be archived.
  • To avoid confusion, we have disabled the New Field menu item when you are in the board layout.
  • Copying the contents of a board is now possible via cmd+c. To copy everything, combine this with meta+a to select all your cards.

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

 

See more

Since we introduced the new GitHub Issues earlier this year in a private beta, we've been working hard to expand access to all developers in order to make GitHub the best place to plan, track, and manage your work. Today, we are really excited to announce that we're moving into a public beta, and now everyone on GitHub.com has access to the new project tables and boards. 🎉

We've used the past few months to work with our private beta users and continue to build up the capabilities of project planning on GitHub with the ability to convert a draft issue to an issue, do bulk actions in tables and boards, automate repetitive actions, set your team's tempo with iterations, and so much more. Along with the new Issues being available for everyone, we're shipping these new capabilities to you today:

📬 Live updates

Collaborate with your team in real-time! Now projects will update as you work so you never miss a thing.

This feature is rolling out gradually, and may take a few weeks to get enabled for your projects.

live-updates

🌐 Public Projects

Public projects let you share what you are working on with the world. Whether this is your team's roadmap, a list of items where you're seeking feedback, or the current work you have in progress – public projects help you work with your community.

  • Project admins can now toggle between public and private visibility in a project's settings screen.
  • Quickly see if a project is public or private via the lock or globe icon next to the project name.
  • Public projects will only show public items, any issues or PRs added from private repositories will be redacted. This includes any metadata added to them in the project view.

public-projects-setup

📊 Insights

Our new burn up chart is designed to help teams visualize progress towards completion, understand development flow, and provide early warning of potential bottlenecks.

This capability has been released as a limited alpha. More organizations will be added in the future.

Insights-alpha

✨ Bug fixes & improvements

We have a whole bunch of improvements for you, including:

  • GitHub Apps support, available as part of the organization projects permissions scope.
  • Projects can now be created under user accounts in addition to organization accounts – head to the projects tab on your profile page to get started.
  • Increased the number of views a project can have to 42 📈
  • Bug fix: removed unnecessary blank rows at the bottom of the table layout.
  • Bug fix: select all (meta+a) works when you are in the No Status column of the board.
  • Resolved scrolling problems in Safari, especially in group by.
  • Added the ability to applysort and group by in the view menu. (Previously you could only clear these in the view menu – which was very confusing!)
  • Archive all cards in a column via a new option in the column header menu.
  • Improved how , is handled in the filter bar which now correctly triggers a new OR search.
  • Custom fields are now clickable in the board layout to quickly apply a filter. (This was a major request!)
  • Row highlights are easier to dismiss with the esc key.
  • Draft issues are included as issues when filtering for is:issue.
  • Hide a grouped column in the table layout.
  • Closed issues are now purple 💜.

Thank you so much to everyone who has helped us with feedback during the private beta 🙏

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

See more

Our current issue icon colors are a source of constant user feedback, citing confusion with errors, confusion between why Open is green and Closed is red, accessibility concerns and the general scariness of seeing red across the issues index page when a bunch of closed issues is usually a good thing.

As part of our roadmap issue today we are starting a rollout that updates the issue closed icon from red to purple. Please see the roadmap issue for more information and future plans to address all of the feedback we have received.

See more

Since our last update, we’ve continued to improve the GitHub Issues beta to expand the capabilities of both project tables and boards. Here are some of the recent ships:

🌀 Iteration field type

Build tempo with our new field type – iteration. With iterations you’ll find it easy to keep everyone aligned on what’s in progress and make jobs like cycle planning a breeze.

Designed to take the manual pain away from creating new iterations every week, iterations are a smooth and streamlined experience.

  • Create a new field, and select the iteration type. Here you can pick the start date and length of the iteration.
  • Hit save and create, and we will auto add 3 instances of the iteration to get you started.
  • Easily create more in the settings screen.
  • Filter, sort, and group by just like you would any other field.

iteration field

✋ Granular permissions

Project access you control. With our new manage access tab it’s easy to set up the right permissions for your project.

  • Select a base role for your organization – admin, write, read or no access.
  • Manage individual access for collaborators.
  • Support for teams and external collaborators coming soon.permissions

    ✨ Bug fixes & improvements

  • We reduced the number of confirmation toasts to help keep you in the zone.
  • Updated icons for draft and closed PRs.
  • Fixed an edge case where the issue suggester could include the issue you just added, which would result in an error.
  • Cards in the board are no longer selected when performing a meta+click on the title.
  • Bug fix where the e and del shortcuts in the board layout we overriding the repo picking during convert to issue.
  • In the table layout, you can now hide a column that has a group by applied.
  • Previously a new project needed items added before you could add columns – now you can start with columns or items.

See how to use GitHub for project planning on the GitHub Issues page and learn more in the FAQ.

See more

You can now choose to use a fixed-width font in Markdown-enabled fields, like issue comments and pull request descriptions. Currently these fields use a variable-width font, which can make it difficult to edit advanced Markdown structures like tables and code snippets.

To enable, go to your appearance settings and toggle on Use a fixed-width (monospace) font when editing Markdown in the “Markdown editor font preference” section.

fixed-width-font

Learn more about writing and formatting on GitHub.

See more

Since our last update, we’ve continued to improve the GitHub Issues beta to expand the capabilities of both project tables and boards. Here are some of the recent ships:

🤖 Workflows

Remove the repetition with new automated workflows that help you keep your project up-to-date.

  • Select the workflows you would like to enable in the new workflow screen.
  • Customize the conditionals and methods to fit your flow.

There’s more to come! Keep an eye out for more workflows and our workflow builder coming soon.

Workflows

🧹 Archive your completed items

Keep the context, but remove the clutter. Now, you can easily archive completed work.

  • Select one or more items – try cmd+a (on MacOS) or ctrl+a (on Windows/Linux) – to select a whole column.
  • Hit e to quickly archive all the selected items, or use the item menu.
  • Easily see which projects an item used to be part of from the issue/pull request page sidebar

Archive

✨ Bug fixes & improvements

  • Share with your community: public projects is rolling out to some beta users; see how they are already using it here.
  • Make quick updates, copy and paste is now enabled between cells in the table layout.
  • Export your table with select all by hitting cmd+a (on MacOS) or ctrl+a (on Windows/Linux) and then copying the selected items.
  • Bug fix so meta+click works on the board without needing a card to already be in focus model.
  • We now automatically add a space when you jump to a search bar with a filter already applied so you can immediately add a new filter.
  • Bug fix for a problem where a negative filter over a hidden field resulted in the field values not being loaded.

See how to use GitHub for project planning on the GitHub Issues page and learn more in the FAQ.

See more

Since our last update, we’ve continued to improve the GitHub Issues beta to make GitHub the place that developers can plan, manage and track their work. Here are some of the recent ships:

🚚 Bulk select and delete

You can now bulk select multiple items in both the table and board layouts.

  • Use cmd+click (on MacOS) or ctrl+click (on Windows/Linux) to select multiple items.
  • Or try shift+arrow-keys / shift+click once an item is already selected.
  • Then hit the del key to quickly remove everything selected.

Bulk delete

🎨 Custom fields in the board layout

Pick and choose which fields you would like to see when in the board layout. Simply use the view menu to customize to exactly what you need.

custom fields

✨ Bug fixes & improvements

  • Group by is now enabled for milestones!
  • In the board layout, if your no status field is empty, it will be automatically hidden.
  • Empty groups are no longer shown when you are running a group by.
  • When a item in the table layout is deleted, focus is retained within the table to keep keyboard navigation active.
  • Bug fix so the is:open filter no longer hides draft issues.
  • Bug fix to resolve issues when filtering over labels which contained :.

Learn about the Issues beta on the GitHub Issues page or in the FAQ.

See more

Over the past month, we’ve continued to improve the GitHub Issues beta as we work hand-in-hand with our beta users to make GitHub the place that developers can plan, manage and track their work. Here are some of the recent ships:

🗂 Improved filtering

Three new filtering options are now available:

  • Find items that don’t match a query with -. For example -status:done
  • Find items that have null values with no. For example no:status
  • Find items based on state with is. For example is:open or is:issue

All of these new filtering options have type-ahead support in the filter bar and can be found in the command palette with cmd+k (on MacOS) or ctrl+k (on Windows/Linux).

all filters demo

📝 Draft to Issue conversion

You can now convert any draft issue in a project to an issue. Simply use the item menu or edit the assignee, labels, milestone or repository fields.

Convert to issue demo

✨ Bug fixes & improvements

  • Filtering is now possible over hidden fields.
  • The scroll position is reset correctly when changing views.
  • Hitting ‘enter’ on a cell keeps you in the same field and moves you to the row below.
  • Fixed an issue with filtering against fields which contained emojis.
  • Updates to dark mode colors.
  • Adding a new item via ‘tab’ now focuses you on the second column in the table layout.
  • The command palette now allows filtering across all fields.
  • Fixed a bug where deleting a field being used for a sort or group by broke the view.
  • Improved drag and drop to empty columns in the board layout.
  • Draft issues are now included under the is:issue filter.

Learn about the Issues beta on the GitHub Issues page or in the FAQ.

See more