User is moving a story to this status called "Awaiting PRD Elevation" which is a "Completed" category status. When a story goes into that status and puts the issue in a release then marking the release as released --the card automatically goes away from board as well.
We know that when a card gets into a done status and releases it wont show up in board, but on his board configuration he is using this "Hide completed issues after 2 Weeks" feature then why isn't the feature working with this.
That particular story which was moved to "Awaiting PRD elevation" was not 2 weeks old then why does it disappear from board even if it is released. Is there a a way to stop that from happening?
Hi @[deleted] - Take a look at the sub-filter on the board (near the bottom of the board settings page). Often time there is a sub-filter there that excludes cars with a value in the Fix Version field.
@John Funk The sub-filter shows this:
fixVersion in unreleasedVersions() OR fixVersion is EMPTY
Does that override the "Hide completed issues after 2 weeks" feature on board.
What does that Kanban sub-filter field do ? How would that affect the issues to disappear from board if they are released?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The sub-filter is intended to filter out things that you have "released" from your Kanban board and hence do not need to see on it any more.
Note the your sub-filter says "the current fix version is unreleased, or the issue has no fix version" and compare that with what your people are doing: "... and puts the issue in a release then marking the release as released"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, it overrides that. It further filters down any cards on the board based on the main board filter.
The sub-filter tells the board not to show any cards that have a value in the Fix Version field. It a card has been released, it has a value in that field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.