You can now create a branch directly from an issue to begin development work that's correlated to that issue. Branches connected to an issue are shown under the "Development" section, which has replaced "Linked pull requests", in the sidebar of an issue. When you create a pull request for one of these branches, it is automatically linked to the issue.
Create a branch for an issue is in public beta starting today. For more information, see the documentation, or let us know what you think.
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.
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.@next and @previous – easily filter to the next or previous iteration as enhancements to the existing iterations filter @current.>, >=, <, <=, n..*, *..n and n..n.
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.
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.
Other changes include:
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. See how to use GitHub for project planning with GitHub Issues, check out what's on the roadmap, and learn more in the docs.
Since our last update, we have a number of exciting updates to share with you for the new projects experience. Including improvements which shorten the gap between the original projects and our new experience as well as iterating on recent ships, such as iterations and insights, based on your feedback.
Providing context on the why behind and instructions on how to best engage with a given project has now become even easier with the addition of project descriptions and READMEs.
Accessible via the settings page or the new side panel on the right side of your screen, the project description provides a short summary of the project while the README offers a Markdown-enabled space for all the additional details your team needs.
We heard your feedback on iterations and now they are even more flexible 🎉. Start and end dates can be edited after creation and iterations can be set to any length – up from the previous limit of 6 weeks.
Project insights continues its alpha roll out and this week we have introduced additional filtering for burn up charts to make it even easier to get to the insights you care about.
Apply filters directly to your insight reports or use the view menu to generate a report based on the filters saved to the view.
Join the discussion to share your feedback and experience with the insights alpha.
Other changes include:
Outside collaborators can now be added to projects. Outside collaborators who have already been added to at least one repository in your organization will now appear when searching for users in 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.
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.
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:
reviewers to any of your existing views.save changes in the command palette or view menu.The reviewers field is currently read only, with write access coming soon.
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.
Other changes include:
... menu would unselect all cards – making it hard to bulk remove multiple items.-@current now includes items with no iteration – which is consistent with other negative filters.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.
Following our last update, we have a number of exciting updates and improvements being released today for the new projects experience.
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.
linked pull requests to any of your existing views.
We have added multiple improvements for draft issues, you can now:
Then easily convert your draft to an issue in your chosen repository when you are ready.
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.
add projects button to search for a project under the same organization or user account as the repository.
Other changes include:
Group by is now enabled for both assignees and repositories ✨.@current iteration.current label when in group by.See how to use GitHub for project planning with GitHub Issues, check out what’s on the roadmap, and learn more in the docs.
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.
When you are in the board layout, you can now pick any single select or iteration field to use for columns.
column field.
No more disappearing items. When you add an item to a view with a filter, those fields will now automatically be set.
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.
Other changes include:
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.
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.
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.
Other changes this week include:
New Field menu item when you are in the board layout.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.
You can now quickly create a Markdown link in all Markdown-enabled fields, like issue comments and pull request descriptions, by pasting a URL on text that you have previously selected.
Learn more about writing and formatting on GitHub.
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:
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.
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.
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.
We have a whole bunch of improvements for you, including:
meta+a) works when you are in the No Status column of the board. group by.sort and group by in the view menu. (Previously you could only clear these in the view menu – which was very confusing!), is handled in the filter bar which now correctly triggers a new OR search.esc key. is:issue.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.
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.
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:
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.
save and create, and we will auto add 3 instances of the iteration to get you started.
Project access you control. With our new manage access tab it’s easy to set up the right permissions for your project.
meta+click on the title.e and del shortcuts in the board layout we overriding the repo picking during convert to issue.See how to use GitHub for project planning on the GitHub Issues page and learn more in the FAQ.
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.
Learn more about writing and formatting on GitHub.
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:
Remove the repetition with new automated workflows that help you keep your project up-to-date.
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.
Keep the context, but remove the clutter. Now, you can easily archive completed work.
cmd+a (on MacOS) or ctrl+a (on Windows/Linux) – to select a whole column.e to quickly archive all the selected items, or use the item menu.
copy and paste is now enabled between cells in the table layout.cmd+a (on MacOS) or ctrl+a (on Windows/Linux) and then copying the selected items.meta+click works on the board without needing a card to already be in focus model.See how to use GitHub for project planning on the GitHub Issues page and learn more in the FAQ.