Skip to content

Tags, filters, and requirements that stay put

The add-bug dialog accepts multiple tags, bug filters reflect the statuses actually applied by default, and stories generated from requirements are written to the backlog.

Updated View as Markdown
For humans

A short release of the kind of fixes you only notice when they stop happening.

Tagging and filtering bugs

The add-bug dialog takes multiple tags as chips rather than a single value, so a report can be frontend and api at once. The status filter now reflects the statuses Studio applies by default, so the filter bar and the list agree on what you are looking at.

Two places where work quietly disappeared:

  • Story updates preserved requirement links. Editing a story no longer drops the requirements it was generated from.
  • Generated stories reach the backlog. User stories generated from requirements are persisted into the backlog instead of existing only in the generation result.

Also in this release

  • Meeting event titles are preserved when a meeting is assigned, and a meeting can be copied into a story from the meeting view.
Navigation

Type to search…

↑↓ navigate↵ selectEsc close