You can now assign a high priority status to your Issues, automatically pinning them to the top of your pipeline 📌

By assigning a high priority status to Issues, you can highlight important Issues and communicate urgency of work across ZenHub. Surface what to work on first and ensure critical bugs get tackled by pinning issues to the top of the pipeline.

There are 3 ways to set priority on an Issue.

1. Through the Issue card option menu.
2. Multi-selecting cards and applying an action.
3. Within the pipeline selector of an Issue.

A few things to note:

• This is the first iteration of Issue priorities. We understand that some teams have requested more priorities, types of priorities, help with setting priority, and much more customization. We are excited to see how priorities are used and look forward to feedback on how to improve the feature in the future!
• Similar to your current pipelines, Issues labeled as "high priority" should also be kept in priority order.
• This will be in the v2.38.118 release of the extension. Most extensions will automatically update but you can always manually click the Update button in chrome://extensions to get the latest version.

Learn more about Issue priorities here

One more thing! A big thank you to everyone who left feedback on our public product board for Issue priorities! We appreciate and review each and every suggestion to inform our decisions throughout the discovery and design phases.

Make common actions easier and faster to complete with Quick Issue Actions

Save time on repetitive day-to-day tasks with our new Quick Issue Actions, making it easier for you to carry out routine actions on Issues.

With Quick Issue Actions you can:

• Assign an Issue to a user
• Apply labels to Issues
• Set or change the milestone for the Issue

Workspaces Phase 3 has been shipped 🌟

Each team can now create their own Board and pipelines while working from the same repos.

What does this mean for you?

• Create multiple Workspaces for the same repos.
  Individual teams can work from the same repos but follow their own workflow meaning no more compromising on the order and set of pipelines.

• Multiple teams can work on the same Issues at once.
  Work is not always linear and there is often an overlap that might require multiple teams to work on the same Issues concurrently. Workspaces empowers teams to visualize the status of an Issue according to their own process and workflow.

• View the progress of an Issue in every single Workspace.
  Easily update the Issue’s pipeline in your Workspace without compromising other teams’ workflows. Any updates to the Issues or Epics (content, labels, Estimates, etc) are reflected in all related Workspaces. Learn more here

  

We have shipped a few changes related to editing a Workspace in preparation for what we call "Phase 3" but may be better understood as "multiple Boards for the same repos". And with that said...

"There can be only one (Board)"

We wave goodbye to the letter 's' and replace it with... absolutely nothing because a Workspace can only have one Board and a Board can only belong to one Workspace. As mentioned, with Phase 3, the same repos can belong to multiple Workspaces. Click here to view Workspaces within our product roadmap.

🎵It's All About The Streams 🎵

Stream-lining your workflow, that is. You can now jump straight into the Workspace editor through the "Edit Workspace" tab located on the sidebar.

Also, all Workspace editing actions will be handled through the editor. We have removed the "Disconnect repo" icon from the Repo Filter on the Board to help familiarize these actions.

We shipped a small button that holds great power. Close all of your connected Milestones from the Burndown chart in one click!

Remember: with great power comes great responsibility. Make sure the Milestone is complete - to reopen connected Milestones, they must be opened individually through GitHub.

We've fixed dozens of minor UI bugs and introduced new markdown features by implementing a new library 🌟.

Here's a list of stand out changes:

🆕 Emoji support, color blocks, and more!

• Writing out emojis, such as :shipit:, render the emoji's image in Issues.

• 3 or 6 digit hexadecimal color codes show color previews next to the code block. Use a code blocks #5e60ba to render in-line color previews.

• Using <!-- --> displays hidden text in Issues.

  This is helpful when creating Issue templates to provide instructions on best practices for using the template!

🎨 Styling updates

• To make tables easier to scan, there's now alternating row colors.

• Inline code blocks have additional space before them

• Use the <details> markdown option to create sections that can expand and collapse to show/hide information.

<details>
 <summary>Summary Goes Here</summary>
 ...this is hidden, collapsable content...
</details>

🐛 Bug fixes

• Using #issue references in code blocks will no longer create Issue references, but remain as content in a code block.
• Links with the @ symbol will no longer incorrectly mention users
• Using @ symbols inside code blocks will no longer mention users, but remain as content in a code block.
• Links with brackets [ ] ( ) will no longer break mid-link.
• When @ mentioning there's not extra spaces after the username.
• HTML for image upload and styling is supported. If images have custom width/height coded in the image URL they will no longer break.
• Ordered list items now indent properly, including showing sub-nested ordered and unordered lists.

Send us feedback

On Saturday, March 23rd 2019 between 1:00 and 5:00 PM Pacific Time (UTC-8) we will be performing infrastructure maintenance.

What this means for you:

• You can continue to use ZenHub during this time, but might experience disconnect errors.
• You might experience a Board cannot be loaded or Error loading Workspace error intermittently as you navigate. A few refreshes should resolve this during the maintenance window!
• Any changes made during the maintenance window to your Workspaces, reports, or GitHub Issues will be saved.

If you have questions when returning back to work after Saturday, don't hesitate to get in touch!

You can now add a description for each pipeline in your ZenHub Workspace!

Remove uncertainty and improve Board hygiene with pipeline descriptions; team members will now have a clear understanding of what Issues belong in which pipeline, allowing for a clear and consistent flow of Issues across the Board. Learn more here.

We've released a suite of bug fixes this week, including:

• Issue titles and comments properly word-wrap on the Board and in the Issue page.
• File uploads will now properly copy and paste for users on Chrome 73.
• If there is a deleted repo in a multi-repo Board, the Cumulative flow and Control chart will no longer hang during loading.
• Creating Issues/Epics in GitHub with the extension will no longer show a duplicate Create an Epic button at the bottom of the sidebar.
• When creating a Milestone in ZenHub the mouse focus area now goes to the title, not the start date.
• Repo names no longer appears as undefined on hover in the web app Milestone page for multi-repo Workspaces.

Performance

• Loading the Board is also now faster! We no longer render an Issue card's option menu—these will only be loaded when clicked .

The status of a PR will now show open/merged/closed properly on PR cards in the Board. Previously, if a PR was merged, it was appearing open, and when open, it was appearing as closed/merged.