I've a question about the new work sub query feature, mentioned in the release notes.
We're currently using two rapidboards. The first one just contains the work items, released items are not visible there. The reason for this was that we don't want to have a "Done" column with hundreds of entries. For reporting, we a copy of that view that includes the "Done" column, which is mapped to the "released" status.
So the new work sub query sounds like a possible solution for us. I'm just a bit confused about the description within the release notes (I haven't found a section in the documentation about the new feature).
"Finally, Kanban teams will be happy to hear they now have the ability to set a sub-query for the Work mode. This enables one board to contain all of the of issues which have been completed without having to show them all in the Work mode. These issues – usually previously resolved issues – will still be available in the Report mode for tracking progress. A great example for a Kanban team is adding JQL to filter issues which were resolved more than a week ago and only show them in the Report mode, and not the Work mode:"
The example query is: resolutiondate <= "-7d" or resolutiondate is null
My understanding is that the work sub query will narrow down the filter if the rapidboard is shown in the work mode. So shouldn't the example be the other way round? Display just the tickets with a resolution date within the last 7 days or with no resolutiondate set? So shouldn't it be
resolutiondate >= "-7d" or resolutiondate is null
A quick test with the modified query showed up the expected results. I just wanted to make sure that this is the indented way to use it.
Hi Christoph,
You are correct -- the example Work sub-query on the blog post would not be very useful. The better query is resolutiondate >= "-7d" or resolutiondate is null.
So to use this in your case, you want to add a Work sub-query which hides all the 'released' issues in your Done column. That way, when viewing Work mode, you will not see those issues, but in Report mode you will be able to report on them.
Hope this helps.
Cheers,
Michael Tokar [Atlassian]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for pointing that out Christoph, I have updated the blog accordingly.
Regards,
Nicholas Muldoon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join the largest European gathering of the Atlassian Community and reimagine what’s possible when great teams and transformative technology come together. Plus, grab your Super Fan ticket now and save over €1,000 on your pass before prices rise on 3 June.
Register nowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.