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
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
I can understand not wanting to show the entire feature backlog. I would argue that something assigned to an iteration meets the threshold for visibility in the feature timeline.
The text was updated successfully, but these errors were encountered:
I strongly agree! The visualization for feature seem to be affected by the "active" stories under that feature. It should be independent of the stories and based on the active/close status of the feature.
Thanks for the feedback @jdshkolnik and @wpat , we show the features if they are in Active status even when they do not have child stories. Can you check if the Feature is marked as active? If not you can still pull it from Plan Feature pane and drop it on the timeline.
I can understand not wanting to show the entire feature backlog. I would argue that something assigned to an iteration meets the threshold for visibility in the feature timeline.
The text was updated successfully, but these errors were encountered: