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
Hello, there is very nice overview about criterias and their state "assigned" to individual work items in the hub, but is there any plan to allow view from the other perspective, i.e. from the work item point of view.
This is such a great extension, allowing nicely work with acceptance criteria, but as of now, there seems to be no way how to identify e.g. Features that does not have acceptance criteria defined, as existence of acceptance criteria cannot be queried and Hub as such provides "only" view from acceptance criteria point of view and where it is linked.
Filterable view of work items that does not have acceptance criteria, or maybe even combination, like work items that do not have specific acceptance criteria, etc. this still kind of creates bit of gap between work items as such and acceptance criteria, which makes it hard for any quality control mechanism
The text was updated successfully, but these errors were encountered:
Hello, there is very nice overview about criterias and their state "assigned" to individual work items in the hub, but is there any plan to allow view from the other perspective, i.e. from the work item point of view.
This is such a great extension, allowing nicely work with acceptance criteria, but as of now, there seems to be no way how to identify e.g. Features that does not have acceptance criteria defined, as existence of acceptance criteria cannot be queried and Hub as such provides "only" view from acceptance criteria point of view and where it is linked.
Filterable view of work items that does not have acceptance criteria, or maybe even combination, like work items that do not have specific acceptance criteria, etc. this still kind of creates bit of gap between work items as such and acceptance criteria, which makes it hard for any quality control mechanism
The text was updated successfully, but these errors were encountered: