Feature Requests

Subject: Release and location fields will not appear in the embedded filters.

1.  Release and location fields will not appear in the embedded filters.

Posted 03-17-2015 16:47

Release and location fields will not appear in the embedded filters. It would be great if these are also provided. This makes users to filter better based on these fields as well.

Suppose that we have two item types Use case and Test Case. User may related these two item types. The Use case does not have the release but the Test case has the release field. Then we cannot get all the use cases which are related to test cases in a release right?

This is the issue we are facing now.
But in general when we are selecting an item type in sub filter, and that item types has release related field, then the drop down in the sub filter should show the release right? But this is not the case in current JAMA 2014.1.

It would be great if we get this feature.

Thanks and regards,

Praveen Paluri



2.  Re: Release and location fields will not appear in the embedded filters.

Posted 03-17-2015 17:44
I've got a good workaround for you wrt the release field.  In the embedded filter choose "keyword" and then type release: <your release name>  

This will work with any normal field (unfortunately not with location...I agree this would be awesome).

If the release name has spaces be sure to include quotes e.g. release: "Release 1.0"


3.  Re: Release and location fields will not appear in the embedded filters.

Posted 03-17-2015 20:26
Additionally, there is an article posted in the community that explains a bit more about why this functionality works as it does. Interesting, Praveen, that you bring this up now...I was recently talking to a Product Manager about this and were were trying to determine the use cases behind needing this feature.


4.  Re: Release and location fields will not appear in the embedded filters.

Posted 03-17-2015 21:53

Thanks for the quick and effective work around.

- Praveen Paluri



5.  Re: Release and location fields will not appear in the embedded filters.

Posted 04-07-2015 14:42
Unfortunately, the same workaround does not seem to work for the location, from what I can tell.


6.  Re: Release and location fields will not appear in the embedded filters.

Posted 04-07-2015 18:51
You're right, Michael. The workaround will work only for Release. As far as needing location could you describe why it's necessary to be embedded rather than as a condition? (Like I mentioned in a post above, I was talking with someone on our Product team who was curious about the uses cases for expanding options in embedded fields.)


7.  Re: Release and location fields will not appear in the embedded filters.

Posted 07-13-2016 22:43
Upstream relationships to a location would be a use case of embedded filter.  I think....I'm looking to create a bar chart with the number of upstream relationships from Locations B, C, D, etc. upstream to Location A.


8.  Re: Release and location fields will not appear in the embedded filters.

Posted 07-14-2016 21:00
How do you use location for relationships, generally speaking? Components are the only container that can use the Relationship widget.


9.  RE: Re: Release and location fields will not appear in the embedded filters.

Posted 06-09-2017 14:43
Adding my voice for this feature request. We'd like to be able filter based upon upstream relationships. We can do by using an embedded filter and keyword release; but that requires setting the release. We'd like to filter based upon location of the upstream relationship. That way we can just drag around the item and filters dynamically update. Using relationships also allows us to have the downstream item to have multiple relationship (what customer contract requirement ever fit nicely into one release?). Tags could probably do this as well, but that doesn't allow for the drag and drop and auto filter updates.

------------------------------
Andrew
------------------------------



10.  RE: Re: Release and location fields will not appear in the embedded filters.

Posted 12 days ago
Hi,

I am adding my voice for this feature request.

Our use case it the following:

We have project that contains all validation artefacts for our ALM tools. These contain (amont others) buiseness requirements, configuration settings and tests. Each of the tool is handled within a separate component in that project.
All tools share common requirements, e.g. from 21 CFR Part 11. There is e.g. a relation between the requirements from 21 CFR Part 11 and configuration settings or features, which satisfy one or the other requirement.

In the validation phase I want to add a filter to my dashboard containing all requirements, that are not being satisfied by any setting or feature in a specific component (i.e. the component of the tool I am currently validating). This is currently not possible without working around this with tags or other meta-information that would not be necessary if embedded filters were able to filter on the Location of the downstream items.

Anna

------------------------------
Anna Henke
MeVis BreastCare GmbH & Co. KG
------------------------------



11.  RE: Re: Release and location fields will not appear in the embedded filters.

Posted 10 days ago
This is my number-one enhancement ask too. As I've ranted on about before, the way that I think embedded filters should work is that a previously-saved "top-level" filter should be able to be embedded in the new filter one is creating. (And that this "nesting" should extend to several levels.) So that's the ideal but a good improvement to the current situation would be to have "Location" as one of the matching criteria available in the (existing) embedded filter. An example of a Use Case for me is in creating Test Plans: "Show me the Test Cases that have upstream relationships to the Product Requirements located here."

------------------------------
Ian Webb
Enphase Energy, Inc.
------------------------------



12.  RE: Re: Release and location fields will not appear in the embedded filters.

Posted 9 days ago
After a frustrating day trying to clean out some Jama issues (someone linked to the wrong project) this would have been another awesome feature. All I would have needed is a filter to items linking to the wrong project - done!
Without this feature it is much more tedious to find out what is linked to the wrong project. And I am not even sure whether we could have avoided this problem with permissions to users.

------------------------------
Markus Molly
Dynamic Controls
------------------------------