Filter across modules
2 answers
I am considering for RDNG, you have two options "Filter by folder" and "Filter by attribute". so you can first apply filter on a particular folder having all the modules and then apply "Filter by Attribute" -> More attributes-> select Priority->select High.
I hope this helps you.
Comments
Hi Deepali
Which version are you using for RDNG? I can see this feature in RDNG V6.0
Hi Deepali
In case you are not able to view the screenshot , it says " No artifacts match the selected folder or filter"
So here’s what I would do:
On the “Artifacts” page, click on the “Filter by Folder” bar on the right side and click on a folder.
Then click on the “Configure Page Settings” icon on the column header bar in the middle section, and add a column for the attribute you want to filter on. This way you have manual visual confirmation that artifacts in that folder have the attribute values you’re looking for.
Then click on the “Filter by Attribute” bar on the right side. The “Filter by Folder” bar will slide down and should have “is in: <folder you selected>”. Click on “More attributes”, enter/select the attribute name exactly as shown in the column header bar, choose your “contains” or “is any of” or whatever action, and enter/select the values. Then hit “Apply”.
If that doesn’t work, you’re seriously doing something wrong or you're database is screwed up...
Comments
Hello MK
Ah, ok, so the problem is that (most likely) each module in the folder has a subfolder where its artifacts are stored. Unfortunately there is no way to specify to filter recursively through subfolders. You can't do this in JRS either.
1. You can try taking off the folder filter, but then you filter through *all* artifacts in your project area. How bad it performs depends on the size of your project area.
2. You could throw all the module artifacts from all the subfolders into a collection and filter that. But any newly added after that are left out until you throw them in too.
3. You could run a JRS that searches the whole project area. The data will be as old as the synch rate, but it works faster than the first idea and you can post the table/graph to a dashboard.