issues

Today’s Changelog brings improved date filtering and the command palette (beta) to Projects!

📆 Date filter improvements

We’ve improved filters so you can use relative offsets for dates and iterations. Try it out by adding date:@today+7 or iteration:@current+2 to the filter bar.

🎨 Command palette (beta)

The command palette is now available in Projects as a beta release and includes project-specific commands.

With this update, the command palette enables users to navigate Repos and Projects and search for Issues and PRs across GitHub directly from Projects.

Quickly access commands related to the project you’re viewing:

Or search and navigate throughout GitHub directly from a project:

✨ Bug fixes & improvements

Other changes include:

• Ability to clear selection in the date picker
• Provide a keyboard shortcut (cmd+s/ctrl+s) to save a project view
• Visible highlighted row selection when deleting/archiving items

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

Today, we are announcing the general availability of the new and improved Projects powered by GitHub Issues 🎉 🎉 🎉. Since we launched the public beta at Universe last year, we have listened to your feedback and shipped 15 changelogs at a cadence of every two to three weeks.

At a glance, the new GitHub Projects enable you to:

• Plan, collaborate, and track your work close to your code in one centralized place.
• Stay organized with custom fields and spreadsheet-like table or board views.
• Keep your eyes on the prize with visibility into done and remaining work to ship.

Learn more about the breadth of capabilities of GitHub Projects in our blog post.

As usual, with our Changelogs, we’re bringing even more new functionality updates to the experience.

⏱ Quickly gain access to your recently used Projects

We’ve added a section to the projects index page that shows both recently used projects and projects created by the user accessing the page. These two shortcuts are handy in organizations with a large project count, making it easy to get to projects you frequently visit.

👀 Improving permissions management

We’ve introduced a new setting that enables organization owners to toggle the ability to update project visibility to public, giving you more assurance that users won’t accidentally expose sensitive data within a project. 🙌

To enable this setting, organization owners can go to github.com/organizations/<org-login>/settings/projects and select the checkbox under the “Member privileges” heading below.

Use this setting to prevent accidental exposure of sensitive data within a project 🔒💖

✨ Bug fixes & improvements

• Fixed a bug where text surrounded by backticks in the Projects side panel failed to render.
• Made it more explicit that deleting a custom field would permanently delete the data of that field.
• Improved styling on Project views, improved spacing, and added separators between views.
• Fixed a minor UX glitch when users switched from one view to another, where issues appear in the table and then are hidden.
• Searching for a repository when performing an issue transfer no longer requires an exact name match to find target repositories.
• Bug fix on issue comments previously when creating/editing a comment, then using tab to exit the comment field shortcuts would not trigger until a focus was moved again.
• Improved fuzzy search for the label picker on issue pages.

📊 Expanding access to charts for all plans

We are expanding our Insights capabilities to all plans! Charts help you visualize and track cycle velocity, current work status, and complex visualizations like Cumulative Flow Diagrams.

Starting today, all projects (beta) users can access custom current charts! Head over to the Insights tab for your projects to try it out and don't forget to share feedback!

We're also expanding access to time-based charts to allow organizations to visualize trends over time. Time-based charts are enabled for all Enterprise Cloud organizations and existing Team organizations with at least one project. Team organizations that have not used projects (beta) will be onboarded over the next couple of weeks.

Thank you for all of your feedback during the alpha and we hope you'll continue to share your thoughts with us on Discussions.

✨ Bug fixes & improvements

Other changes include:

• File uploads now support both .webm and .tgz file types.
• Unsaved view changes are persisted across page refreshes.

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

This marks 1️⃣ year since our initial private beta announcement! 🎉

Today's Changelog brings you the ability to bulk add items to projects and GraphQL API improvements!

🪷 Bulk add items

To make it even easier to add your issues and pull requests to a project, we have now added a new way to bulk add issues to your projects.

• Hit the + button by the omnibar.
• Select Add item from repository.
• Pick your repository and get adding.

🤖 GraphQL API improvements

The projects GraphQL API is now generally available 🎉. With this update, we are announcing:

1) The introduction of new ProjectV2 object and mutations.
2) The deprecation of ProjectNext object and mutations, scheduled for 1st October 2022.

What are the new changes?

We have added a new ProjectV2 object to our GraphQL API to programmatically access a project.

The fields of the project are now available as:

• ProjectV2Field for a text, number or date field.
• ProjectV2IterationField for an iteration field. The iteration details are available under the configuration object.
• ProjectV2SingleSelectField for a single select field. The details about the different options are available under the options object.

The items of the project are represented by the ProjectV2Item object. It contains a field type to identify the item type – Issue, Pull Request, Draft Issue or Redacted. The values of the item are available under the fieldValues field.

We are also adding the following mutations for updating a project:

• updateProjectV2
• addProjectV2ItemById
• updateProjectV2ItemFieldValue
• updateProjectV2ItemPosition
• addProjectV2DraftIssue
• updateProjectV2DraftIssue

Based on feedback that more granular scopes would be useful, we have introduced new OAuth scopes specifically for this update:

• The read:project scope provides query access to ProjectV2 objects.
• The project scope provides query access to ProjectV2 objects and access to mutations.

✨ Bug fixes & improvements

Other changes include:

• Bug fix where @mentions didn't include all users when editing a comment.
• Ability to open the issues side-panel using the spacebar.
• Long project titles no longer truncate when there is room to display the full title.
• Bug fix to resolve a flash that occurs when creating or editing a project view title.

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

Today’s Changelog brings you tooling to migrate projects from the classic version to beta and accessibility improvements!

🚀 Migrate from Projects (classic) to Projects (beta) (feature preview)

We’ve made it easy for you to migrate your old project (classic) boards to the all new projects (beta) experience! Enable “project migration” in feature preview so that you can try out tables, multiple views, new automation options, and powerful field types with your exisiting projects. For more information, see “Exploring early access releases with feature preview.”

How it works:

• We’ll create a copy of your existing project (classic) board in Projects (beta)
• You’ll be prompted to close your old project as the newly migrated project and old project will not be kept in sync
• You can reopen your old project in a pinch if necessary!

💖 Accessibility Improvements

To provide a more accessible experience for all our users, we’ve made numerous fixes across key table and board workflows to better support users leveraging keyboard navigation, screenreaders, or high magnification. Some updates include:

• Ensuring previously unreachable elements, such as suggestion lists and column headers, are reachable via keyboard navigation and appropriately handled by screenreaders
• Updating tab behavior in table views to be consistent with common practices for spreadsheet-like tools
• Improving the Add item workflow by updating the alignment and overflow behavior of the results list to be viewable at high magnifications

We’ve still got work to do but we’re excited to continue making projects better for all our users.

✨ Bug fixes & improvements

Other changes include:

• Sorting by reactions on the issues index page now includes the number of reactions added
• Updated naming conventions for assignee in header when grouped in table

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

Today's Changelog brings you the release of project webhooks, a first exploration into templates and a host of improvements to GitHub Issues.

☁️🪝 Automate more with project webhooks

The first release of webhooks for projects (beta) is now available for Organizations and GitHub Apps. 🤩

Once configured and enabled, webhooks will transmit events for any action taken on project items within your organization. This includes changes made (via projects) to status, assignee, labels, and even draft issue titles and descriptions!

You can find webhooks for projects (beta) in the "Webhooks" section of your organization settings page under the title Projects v2 Items. For more information, including technical specifications, check out the docs.

🦻 We're still developing webhooks, and we'd love to hear your feedback; drop us a line in our Feedback Discussion.

🎨 Get started with templates

When you create a new project, you now have the option of multiple templates to choose from. Start with either the default table or board, or explore one we've created for you with our team backlog or feature templates.

Stay tuned for more with templates in the future. 💖

🧭 Improved navigation via project header

Quickly understand which organization or user a project belongs to and easily navigate via the breadcrumbs in the project header. We've got more to do here, so please let us know what you think.

✨ Bug fixes & improvements

Other changes include:

• Bug fix so projects (beta) insights retain URL parameters when switching to custom date ranges.
• REST API, GraphQL API and webhook support for closed issue reasons.
• The emoji menu on milestone creation now loads in the correct place.
• Users trying to upload large files now receive the correct 'file too large' error, not a 'file type not supported' error.
• Bug fix when converting a task list item to an issue, the ` character is now correctly formatted.
• When transferring an issue between repositories, if no search results are found there is new UI to help you understand why some repositories are excluded.
• Using the assignee filter menu on the issues index page, you now have the option to filter by the current user instantly, without having to wait for all possible assignees to load.

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

Today's Changelog brings you the release of issue closed reasons, project deletion, and availability of the new side-panel.

🕵🏽‍♀️ Issue closed reasons

We announced a preview of issue closed reasons in March and today, we're releasing them to everyone. 🎉

Issue closed reasons help you communicate the why when closing an issue:

• When closing, you can opt to close as complete (default option) or not-planned.
• When filtering, adding a reason will allow you to filter down to the specific set you need with either reason:complete or reason:"not planned".
• We have added a new state_reason attribute to our REST API, GraphQL API and webhooks. These are currently in preview and will be fully shipped in the upcoming week.

✂️ Delete projects you no longer need

While you've been able to close projects, we heard you loud and clear that it wasn't enough and we're now introducing the ability to fully delete a project. Keep your project lists tidy by deleting experimental or out-of-date projects that are no longer relevant to you and your team.

💥 Side-panel enabled for all projects (beta) users

In our last changelog, we introduced the projects side-panel as a feature preview users could choose to enable.

After seeing users flock to enable this feature and lots of great feedback in our side-panel discussion, we've decided to enable this feature by default.

Expect continued improvements in the side-panel experience over the next few months. ☀️

✨ Bug fixes & improvements

Other changes include:

• Added a Copy link button to the sidebar for easier issue sharing and enabled keyboard shortcut (Space) to open the side panel.
• Fixed various bugs around syncing information between the project and side panel.
• Fixed full-height Markdown editor for drafts.
• View and edit projects (beta) custom fields on GitHub Mobile.

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

Today's Changelog introduces several updates to the projects (beta), including the highly requested side-panel, and other improvements!

💥 Direct editing and comments with side-panel

You spoke, and we listened!

This first iteration of the new side-panel in the new projects includes all of the functionality you're used to: editing issue descriptions as well as modifying labels, assignees and milestones.

Directly from the side-panel, you can now…

• 💬 read and leave comments
• ⚙️ edit project custom fields
• 🤠 react to issues and comments with emojis

Check out the projects side-panel by enabling in your feature preview. Once you try it out, we would love to hear your feedback in the corresponding feedback discussion!

🔍 Improvements to adding items under filtered views

We've improved the experience working within filtered views! Now when you add a new item to your filtered view, instead of disappearing, projects automatically matches the metadata of the new item to the metadata of the row above it.

🤩❤️👀 More Emojis! ✨💥🥳

Coming soon! We've added the ability to access the GitHub emoji picker from anywhere in projects. Once launched, type : into any project text field to check it out.

We continue to iterate and address your feedback for GitHub projects (beta) and in this week's Changelog we are including improvements to our settings and insights features.

⚙️ Create and delete fields from the Settings page

Previously, you could only create and delete fields from the Table view, but with today's update, you'll be able to add and delete fields directly from the Settings page.

Group by custom fields for time-based charts (alpha)

Project insights now supports the ability to Group by custom fields for time-based charts, giving you the power to analyze trends over time for the fields you care about most.

✨ Bug fixes & improvements

Other changes include:

• Bug fix to resolve drop-down arrow illogically persisting after grouping by a field then sorting by a different field.

Our latest updates to the projects (beta) experience include the highly requested ability to bulk add issues and pull requests to a project as well as an explorable archive and a new GitHub Action! ✨

✅ Bulk add issues and pull requests

Selecting one or more items from either the issues or pull requests repository index pages now provides the option to bulk add to a project. When items are selected, the top menu bar will now includes the option Projects (Beta) where you can select any of your available projects to add your issues and pull requests to.

🧭 Explorable archive

Archiving allows you to keep long lived projects focused on upcoming ideas while preserving custom metadata if an item is no longer relevant (for example, it is part of a completed iteration).

​With our new explorable archive you can:

• Use the filter bar to quickly parse through all the items in your archive.
• Automatically bulk restore or bulk delete items from the project archive.
• From today forward, you’ll be able to see who archived an item and when it was archived.

🪄 “Auto-add to project” GitHub Action

We’ve released a beta version of an official GitHub Action for automatically adding newly opened, labeled or transferred issues and pull requests to a project.

Adding issues or pull requests to your project is as easy as creating a simple workflow in your target repository and watching the issues and pull requests auto-magically 🪄 roll in.
​
Check it out in the GitHub Marketplace or go straight to the README.

✨ Bug fixes & improvements

Other changes include:

• Bug fix for pull requests to open in a new browser tab by default when selected from a project (this now matches the current behavior for issues).
• Minor updates to the draft issue editing experience to align it with the current issues experience. Additional updates to improve this further are coming soon.
• Projects (beta) now appear under the repositories section of the projects picker, making it easier to add an issue or pull request directly to a project.

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

Today, we are sharing new updates to the projects (Beta) experience, including updated repository filters and custom charts for project insights. We are also sharing a preview of issues closed reasons coming soon across GitHub.

🗂 Index page filtering

When in your issue and pull request repository pages, you can now use filters to see which items are or aren't included in a given project, making it simple to filter down to just the items you are looking for.

• Select a project from the filter menu to see all the issues or pull requests already included in the selected project.
• Add - in front of your project filter to see all issues or pull request that are not included in the selected project.
• Try no:project to see all issues or pull request that are not currently in a project.

🏗 Custom charts

We've continued to build upon the insights alpha based on your feedback. We are following the releases of persistent charts and chart filters with the introduction of custom charts. 🎉

Custom charts allow you to generate the insights you need with six different layout options, configurable grouping and the ability to display any of your custom fields.

With custom charts you can:

• Create a column chart, grouped by iteration and summed on effort to show how much work is going into each iteration.
• Understand where your attention is focused with a stacked column chart grouped by a custom field.
• View trends over time with the stacked area or line chart.

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

🕵🏽‍♀️ Issue closed reasons

Last year we introduced updates to our issue icons and colors along with the commitment to address your feedback on showing the reason why an issue had been closed.

Today we are starting to roll out a preview of issue closed reasons to a small group of users.

• When closing an issue, you can opt to close as complete (default option) or not-planned.
• When filtering for issues, adding a reason will allow you to filter down to the specific set you need with either reason:complete or reason:"not planned".

✨ Bug fixes & improvements

Other changes include:

• In case you missed it, support for creating a branch for an issue was recently released.
• Copy support is now included for Linked pull request and Reviewers field types.
• Bug fix to allow the viewing of insights immediately after project creation.
• Bug fix to resolve sort order being lost when a column is hidden.
• Resolved a problem with the copy shortcut when multiple off-screen rows are selected, to ensure all off-screen data is copied.

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

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.

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.

🎨 Project descriptions

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.

🌀 Flexible iterations

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.

📊 Insights filters

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.

✨ Bug fixes & improvements

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.
• The top right menu bar has been collapsed and additional options have been added including the ability to see the latest Changelog updates and the Docs pages.
• Bug fix to resolve the creation of duplicate draft issues which could occur when double tapping the enter key.
• If an iteration start or end date exists in a different year to the current calendar year, the year will now be shown along side the iteration.

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.

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