You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's no easy feat to search and triage issues across repositories when you have many teams working towards a shared goal. Issue types will allow users to classify and manage different types of issues across repositories.
Intended Outcome
Some folks have tried to use labels in order to do this - however labels are tied to repositories and label syntax can drift across repos. This makes triaging issues across repos difficult.
We believe that by creating a shared language to standardize work items across repositories we'll unlock reporting and automation use-cases.
How will it work?
Users will be able to define issue types (ex. bug, feature request, spike) at the org level and apply this syntax to an issue in a repo.
The text was updated successfully, but these errors were encountered:
Summary
It's no easy feat to search and triage issues across repositories when you have many teams working towards a shared goal. Issue types will allow users to classify and manage different types of issues across repositories.
Intended Outcome
Some folks have tried to use labels in order to do this - however labels are tied to repositories and label syntax can drift across repos. This makes triaging issues across repos difficult.
We believe that by creating a shared language to standardize work items across repositories we'll unlock reporting and automation use-cases.
How will it work?
Users will be able to define issue types (ex. bug, feature request, spike) at the org level and apply this syntax to an issue in a repo.
The text was updated successfully, but these errors were encountered: