Skip Navigation LinksHome Page > Forums > SpiraTest Forums > SpiraTest Issues & Questi... > Requirements Filtering Dr...
To whom it may concern,
For some reason when I am on the Requirements Main Page and I select a filter on the left-hand side, the dropdowns to access the lower level requirements no longer work and the only way to get it to work is to do a manual refresh. Has anyone else come across this? We have 600+ requirements and need to use the filtering feature.
Warmest Regards,
Vasu
Hi Vasu,
Have you tried rolling back if you have recently updated? This might fix the issue at ease.
Kind Regards
Pasu
Based on the view count this is rapidly becoming a hot topic!
Hopefully one of the Spira Experts can help us to solve this issue.
Warmest Regards
Pasu III Jr
We haven't heard of this issue before. Could you please provide more details? Exactly what steps are you taking? Can you explain what you mean by "the dropdowns to access the lower level requirements no longer work".
What version of SpiraTest do you have? What browser are you using?
Thanks!
Elise
How do I upload an image to this forum?
It is much easier to explain this with a screenshot.
We are using SpiraTest version v5.4 and I am using Chrome.
Unfortunately, images can't be included in forum posts.
So you have two choices:
A. try to explain the issue in words here in the forum, or
B. Create a help desk ticket. You can include images in tickets.
Okay I'll have a go at explaining in words.
When in the Requirements main page, on the right hand side you can filter the requirements based on Components. Once I select one of these components SpiraTest successfully filters out the other requirements that are related to the other components. The requirements tree is now fully expanded such that you can see all requirements for that component. I attempt to collapse parts of the tree which works, but as I attempt to expand the tree it does not (not even a loading bar on the top right). Particularly I try to expand a package that only contains packages, if I expand a package with requirements it seems to work.
Hope that is a clear explanation.
Cheers,
Jerome
Hi Jerome,
Ah, yes, now I understand. When a filter is on, and you collapse a package, sometimes then when you try to expand it again, nothing shows under it. That's how the requirement list has always worked. As you said, it happens when you have only sub-packages under the package. When you filter requirements it only displays packages that have a child item that matches the current filter. However since the intermediate item is not expanded when you expand the top-level item, it hides the intermediate folder (since its children are hidden). You can use "show all levels" to work around it. Or you could set the rows per page to 500, in order to try to avoid collapsing packages.
Regards,
My packages, sub-packages and requirements are all defined as the correct filtered Component and the sub-packages still get filtered out, that looks like an obvious bug that should be addressed.
And if you have any questions, please email or call us at +1 (202) 558-6885