Forum Discussion
Combining filters on multiple fields
- 6 years ago
So, after bashing my head against this for the best part of a month, I have finally come up with a somewhat 'cludgy' solution, that at least gives me what i want, and as usual - it was far simpler than i had been making it!
Ultimately - I have created a new column, which combines the status and issue type into a string - i am then using that as a filter for my graphs. It's not pretty, but it is proving functional, and allows me to filter down my fact table to show - for example - all stories at dev done AND all spikes at closed.
Thank you for providing example data. I will continue to help work through this with you if you want. Here are images of what I was talking about to try to simplify and harmonize the two workflows. I know this is oversimplified but just trying to better understand your goal. Can you provide an example output with the rights answers so I have something to shoot for with a potential new DAX expression? Are you looking for a new DAX table? Measure? Visual with measure?
Short version:
So i am pretty agnostic about "how i get there" but in terms of the solution, i had been trying to create view of the history_sprint_summary table that is filtered down to the selected status (from my status slicer), and any tasks that have moved to closed for each iteration period. Ultimately i want to produce a graph like the one below, that shows work done per iteration, and that the user can drill down to see the items.
Longer version:
I am trying to produce a graph which will show me a trendline of Story Point, Story Count and Cycle Time over a number of iterations. Currently this works fine by using the history_sprint_summary table, but as i said, i am then allowing the user to filter on end status (e.g. dev done - it could easily be Ready for Live, or any other status). I would also like the user to be able to right click the data points to be able to see what items go to make it up.
So far so good.
Stories have a workflow of "Backlog, Ready for Dev, In Dev, Peer Review, Ready for QA, QA, Release Test/UAT, Ready for Live, Closed
Tasks have a workflow of To Do, In Progress, Closed
As you can see, the problem with that is that the tasks never go through Dev Done (the usual dev reporting point) or many of the other workflow statuses. As i said above - I want to have the graph above that shows work done per iteration, allowing the user to select the workflow status they report at (e.g. Dev Done), but also, i want to include for every data point, all tasks that moved to closed in the same period. I can't show everything that moved to closed - as the story workflow also uses the closed status.