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
In staging workflow, if a request has been pushed to Excluded backlog (ie ignored) and is then superseded by another request, the initial request is not removed from the excluded backlog and is still visible there and in the staging dashboard.
The text was updated successfully, but these errors were encountered:
It's debatable if the superseded one should automatically end up in the active backlog or the excluded list (IIRC, the old tooling kept the request ignored)
that's why I made this a feature request - the old behaviour is preserved. I think the idea is to have the old ignore reason visible to decide what to do with the followup. But then again, that ignore reason we also put in as comment on the request, so just killing superseded requests from exclude list sounds acceptable.
In staging workflow, if a request has been pushed to Excluded backlog (ie ignored) and is then superseded by another request, the initial request is not removed from the excluded backlog and is still visible there and in the staging dashboard.
The text was updated successfully, but these errors were encountered: