Create an @Backlog item similar to @CurrentIteration than I can use to create queries for use by mutliple teams.
I have four teams, all working on the same project in different product areas. The work is sliced up using iterations, so each team has its own backlog iteration with sub-ordinate sprints. We have a specific sprint named 'Backlog' to improve filtering under each.
@CurrentIteration is great for some things, but I want to create queries based on a teams backlog (such as all user stories not under the backlog iteration with a link to a risk item).
If I had an @Backlog term, I could create a query that would work for all teams, rather than having to create seperate queries for each and manage them every time we finish a release and move to another iteration. I would simply need to set the teams backlog iteration.
AdamC
shared this idea
1 comment
-
AdamC
commented
Addendum, to work well I would need to be able to use terms such as 'not under - @Backlog&"\non functional" ' So a path extension statement as well.