Skip to content

GitHub Issues & Projects – April 6th update

Today's Changelog brings you bulk editing in the table layout and improvements to tasklists!

🦖 Bulk editing in tables

You can now update multiple cells in a column at once!

Update a range of cells in any column by dragging the small blue rectangle in the bottom right of any cell up or down. You can also use keyboard commands to paste values into multiple cells at the same time.

  • 1⃣ Copy a value, using Command+C (Mac) or Ctrl+C (Windows)
  • 2⃣ Select a range of cells by clicking on a cell, holding Shift and clicking a different cell in the column or select non-neighboring cells by clicking a cell and selecting multiple cells while holding down Command (Mac) or Ctrl (Windows)
  • 3⃣ Paste values into selected cells, using Command+V (Mac) or Ctrl+V (Windows)

✅ Tasklist lockless editing & live Projects updates

The hierarchy team has been hard at work improving tasklist performance on issues and in the Projects sidepanel speeding up editing and control of tasks by 2x! We call this class of improvements "lockless editing" and we're working on baking this approach into all tasklist operations in the future.

We've also improved the speed of tasklists updates reflecting in your projects. Changes to the Tracked by and Tracks columns, which could previously take minutes are now reflected in real-time. 🎉

🐞 Tasklist bug fixes and improvements

  • Added a confirmation dialog when selecting the "Delete Tasklist" option in the three-dot-menu
  • Added a toast to prevent users adding more than 1,200 items to their project (the current project limit) when grouped by Tracked by
  • Improved logic and handling of issues with long titles and multiple labels
  • Fixed the item state icon when a Tracked by issue is closed as not planned
  • Increased the width of the Tracked by filter suggestion so users can now read the entire issue title without truncation
  • Added support for issue deletion and transfers within tasklists and issues with tasklists
  • When filtering by Tracked By in your project, items added will now show up in the last tasklist of the issue you are filtering by
  • The tasklist button in the Markdown toolbar now accepts other kinds of list types as well as titles when highlighting text and clicking the tasklist button
  • Fixed an error where some users weren't able to see issues with tasklists in the Tracked by search menu in the project filter
  • Fixed a bug where private issues were being displayed when grouped by Tracked by
  • Fixed a bug where completion data for the Tracks column was stuck in a loading state
  • Fixed an error where tasks were sometimes "reverting" to previous state after a user action
  • Fixed a bug where users who did not have write-access to the repository, but did have write-access to the issue were not able to access the tasklist omnibar
  • Fixed incorrect display of the Tracked by pill in the project item side-panel

Bug fixes and improvements

  • Enabled scrolling on the project description panel
  • Added the Repository field pill to board items when toggling it from the Fields menu
  • Fixed project and workflow filtering to support unmatched quotes
  • Fixed a rendering issue when displaying multiple field sums
  • Fixed a bug where some Mermaid diagrams were not rendering in the projects side-panel
  • Fixed a bug where leading whitespaces caused a filter to error

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

GitHub's navigation has been redesigned with a new look and improved user experience, and it's available to try in beta.

New breadcrumbs provide a clear understanding of your location within GitHub and its information architecture.

Screenshot of the navigation UI, highlighting the breacrbumbs

Streamlined menus:

There's a new global menu designed to highlight common workflows.

  • You can quickly access links to your dashboard, Issues, Pull Requests, and Discussions, as well as your repos and teams.
  • Your lists of top repos and teams are ordered by your usage, and can be expanded and filtered to quickly find what you're looking for.
  • Access it by clicking the GitHub logo in the upper left corner.

The user menu has likewise been updated with a new design.

  • We've added links to documentation and customer support.
  • You can still access it by clicking your user profile in the upper right corner.

Screenshot of the navigation UI, with the left menu open to reveal the navigational links

The redesigned navigation is optimized to work with the new code search experience and introduces a button to quickly access the command palette.

Faster, more consistent, and more accessible

Under the hood, we have completely rearchitected the navigation across every feature to be faster and more consistent. It's also more accessible, built from the ground up to work with assistive technology.

Join the beta

To access the beta version of our redesigned navigation, go to Feature Preview and enable "Global navigation update."

See more

We're excited to share four improvements that we think will improve how moderators maintain their communities. Our goal with thesse improvements is to help moderators of large communities distribute the workload of maintaining healthy discourse. The improvements we're proposing are:

  1. Allowing users with the triage role to make the following changes (only within Discussions):
    a. Move Discussions to a different cateogory
    b. Convert Issues to Discussions in bulk
    c. Hide Discussion comments
    d. Edit and delete Discussion comments
  2. Allowing users with the triage role to report content. (Impacts Discussions, Issues, PRs).
  3. Let prior contributors be able to report content by default in new repos. (Impacts Discussions, Issues, PRs).
  4. Maintainers can choose to let ALL users report content. (Impacts Discussions, Issues, PRs).

The first two changes to the triage role impact existing users with that permission. These changes slightly increase the scope of what the role can do – but we believe that these changes are consistent with how the majority of maintainers are trying to use the triage role.

Changes 3 and 4 impact who can report content by default. Moving forward, new repos will get a better default (letting prior contributors report content), but ultimately, we're putting the power in the hands of maintainers to decide how best to run their communities.

For questions or feedback, please visit our community.

See more