Skip to content

GitHub Issues & Projects – April 27th update

Today's Changelog brings you an easy way to set base project permissions and tasklists improvements!

🧑🏻‍🤝‍🧑🏾 Set Base Permissions in Projects

Organization admins can now set default project permissions. Project admins can always update permissions on their projects, but by changing the base permission, organization admins can change the default between admin, read, write or no access upon project creation.

🐞 Tasklists Bug Fixes

Thanks to your continued feedback we continue to make improvements for our tasklist users week over week!

  • Fixed a bug in projects where navigating to an item in the tasklist, going back to the parent, then navigating back to the same item was resulting in a strange and broken display
  • Fixed a bug where interacting with meta-data edits on tasklists too quickly resulted in users being pushed to a nonsensical blank page
  • Fixed a bug where clicking on labels in tasklists sometimes changed their order
  • Fixed a bug related to converting issues where sometimes draft tasks were not displayed as an issue until after the page was refreshed
  • Fixed a bug where users were unable to make changes to item meta-data after dragging and dropping items in the tasklist
  • Fixed a bug where converting too many issues at once sometimes broke tasklists
  • Fixed a bug where dragging and dropping while the tasklist was syncing resulted in the drag and drop not being registered
  • Fixed a bug where changing meta-data while converting an issue made the meta-data not reflect on the tasklist
  • Fixed a bug where pressing ESC when changing metadata resulted in weird UI

Bug fixes and improvements

  • Improved speed on copy and paste behavior in the table view
  • Fixed omnibar margins and positioning in the roadmap layout
  • Workflow save button validation check now works without needing to refresh the page
  • Fixed several filter bar bugs
    • Clicking on the assignee icon no longer removes the assignee:@me filter
    • Clicking on milestones with a no longer ? depopulates the filter

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

Fine-grained PATs can now call the GitHub GraphQL API. This was a limitation at the start of the public beta, and is now supported.

Like with the REST API, the resource owner set for the token must match the owner of the resource being accessed. For example, when you want to look up a specific repository in GraphQL:

query {
  repository(owner:"octocat", name:"Hello-World") {

The resource owner would need to be octocat to succesfully run the query.

In addition, GitHub Apps now have read access to public resources via GraphQL by default when using user-to-server tokens. This is true even if they are not installed on the organization or user that owns the resource.

This change brings consistency to the access control between REST APIs and GraphQL APIs for GitHub Apps. We made similar changes previously for REST APIs which you can read more about here.

To learn more about GraphQL, see "About the GraphQL API". For more details about fine-grained PATs, see "Creating a fine-grained personal access token". And finally, to learn more about GitHub apps, see "Setting permissions for GitHub apps".

See more

You can now create new repositories with pre-filled form fields, making it even easier to define the right info for your new repos from the start.
There are a number of query string parameters available, including:

  • name
  • description
  • visibility
  • owner
  • template_name
  • template_owner

To get started you can craft a query string at the end of starting with ? followed by the fields and their values.

See the example below for more details:

Learn more about Creating a new repository

We appreciate your feedback in GitHub's public feedback discussions

See more