Hi all,
I would like to use a filter to display our backlog. What we want to do is to display all the stories that are assigned to a future Iteration or the Iteration is Not Set.
I tried to do something like this using a project variable in the Advanced Filter Tab but it is not working:
- Type = Story AND (Iteration > NUMBER ('Current Iteration Number') OR Iteration = NULL)
This is working fine:
- Type = Story AND (Iteration > NUMBER 49 OR Iteration = NULL)
Do you know if there is another option to do that?
Many thanks,
Ariel.
Comments
9 comments
Ariel
What you see in this case is correct because I think 'Iteration' is a card relationship property and (Current Iteration Number) is a numeric project variable and so they can not be associated with it.
As for the greater than not working correctly which you mentioned in your earlier posts, I have tried to reproduce this issue and have been unable to do so. I expect that the problem might be that your "Iteration 0" has a card number that is greater than 49. I think this because "Iteration > (Current Iteration)" looks for cards that have their Iteration property value card number greater than the card number of the (Current Iteration).
Could this be the case?
- Suzie
Ariel
I have tried to reproduce this issue a couple of times and have been unable to do so, even if I look soley at Iteration 0 at the issue. If you would like help resolving this issue it would probably be more productive to get in contact with our support team who could look at this in more detail for you.
I hope that we can help out.
- Suzie
Hi Suzie,
I did the following and this fixed the error, but I think the problem is still there.
The iteration 0 had the #2. And the #1 was deleted, so the #2 Card was the first one for our project(probably the error is related with this??).
I took another card (#30) and then I changed the type from task to iteration. Then I assigned all the stories to this "iteration" (smaller than #49) and then I applied the advanced filter:
That works fine. At least I could found a workaround for this problem :-)
Many thanks for your help,
Ariel.
Hey Ariel
Is the property variable value a card or a number? If this is a card, I think this should work if you remove NUMBER in your first example.
Please let us know if we can help more.
- Suzie
I believe your issue is syntax. When referencing a project variable, my understanding is that you do not precede with NUMBER, and don't wrap it with quotes (I'm assuming that 'Current Iteration Number' is the name of a project variable you have defined, which is numeric in type).
Try the following (a test of essentially the same syntax works for me on Mingle 2.2):
Type = Story AND (Iteration > (Current Iteration Number) OR Iteration = NULL)
Hi thanks for your help.
I will explain a bit more why I´m doing this.
I have two project variables:
- The first thing I tried was the following query:
Type = Story AND (Iteration > (Current Iteration) OR Iteration = NULL), but looks like the ">" is not working as expected. Results from Iteration 0 are retrieved... and that is wrong. (see last image attached). I think probably Mingle is using another concept for bigger.
- The second thing I tried is using the (Current Iteration Number) PVL, because the greather than comparisong works fine for numbers:
Type = Story AND (Iteration > NUMBER ('Current Iteration Number') OR Iteration = NULL) but this throws an error as I posted in the first message
- The approach which is working very good is the following:
Type = Story AND (Iteration > NUMBER 49 OR Iteration = NULL), but the problem is that every iteration I will need to update this Filter instead of the Project variable.
Thanks again,
Ariel.
Hi suzie,
I tried what you said and looks like the problem is with iteration 0 only.
These are the iteration´s numbers:
See the image attached and the filter applied.
I also changed the current iteration to "Iteration 3", and the results contains stories from
Thanks again,
Ariel.
Hi Mike,
This is what I get: Filter is invalid. Comparing between property 'Iteration' and project variable (Current Iteration Number) is invalid as they are not associated with each other. Help Reset filter
Remember that Current Iteration Number is a PLV with value = 49
Thanks again,
Ariel.
Hi, Ariel,
Based on your description, I believe my syntax from my previous comment will work in your case. Can you give it a try and report back on results?
Please sign in to leave a comment.