How to use Relationship Rules

By Knowledge Base posted 03-08-2016 04:59

Relationship Rules allow you to restrict and allow which items in a project can be related to each other.  

In order to configure a set of Relationship Rules you will need to be an Organization Admin. You can find the Relationship Rules menu under Admin > Relationships.
Relationship Options will allow you to toggle the Status and Note fields in the Relationship widget in an item’s single item view. The Status field will allow you to define a status of the relationship (more on this below) while the Note field will allow you to leave a note to accompany the relationship. Relationship Types is the pick list with the types you will be able to set to each rule. None of them have functional differences. They are purely to label different types of relationships and are customizable. To make Note and Status fields visible in the widget make sure Show Note and Show Status in the Relationship Types section is set to true.

To add rules, select Add Rule Set then Add Another Relationship. The Upstream and Downstream drop down menus will list all of the items you have available in your Organization. The Upstream and Downstream columns will dictate which direction the items can be related. It is possible to create the same relationship in both directions using two entries. As mentioned above, the Relationship Type does not have any functional purpose. It is for differentiating types of relationships with a label.

When setting relationships, you will have the option to make it For Coverage by selecting the checkbox. When it is For Coverage it will allow the Relationship Status Indicator to trigger if a required relationship has not been satisfied or there is an orphan item. As of 2015.2 you will need to resolve all of the item's relationship needs as outlined in the Relationship Rules to toggle this indicator off. You will see one of the two below images in single item view indicating this depending on your version of Jama.


To add a project to a Rule Set, select Add Project next to the rule set's title. Multiple projects can share a relationship rule set to keep it consistent. One Relationship Rule Set can be assigned per project. Additional rules can be added to the existing rule set if more are required.

To edit a rule, select the rule you would like to change and it will become editable. Make the changes you wish and select Save to apply. To delete, select the X icon next to the rule.

The selection at the bottom Allow relationships with item types not in this rule will allow any item not listed in this rule set to be related with any other item not in this rule. It will not affect the existing relationship rules.



2 days ago

I am a new member into this community. I  would appreciate any guidance on the issues below, including links to previous threads on these items using JAMA API.
A) Traceability/Relationship between:
1)  Requirements and Test Cases
2) Requirements and Releases
3) Release and Test Cases
4) Release and Test Plans
5) Release and Test Cycles

B) On the UI, in 8.56.2 version,  I see 'testcases' as an endpoint (?). I do not see it in the list of endpoints documents. What am I missing here?


06-04-2020 07:00

Can you elaborate for me on what specific Boolean operations are used to determine whether For Coverage items are listed as Orphan or Missing Downstream? (particularly if there's a verification type that's meant to verify more than one type For Coverage)

I see many examples in training material in which mutually exclusive item types (e.g. Functional requirements and Non-functional requirements) are both verified (for coverage) by the same verification type. Yet, when I try something similar, I get flags for Orphan or Missing Downstream that don't make sense to me. Thanks!

03-10-2020 07:21

​Is it just me or are these images unreadable? Perhaps the links to images have been wiped out (since it's 4 years old), but it was be nice if they were legible. Thanks!

04-19-2016 09:52

I believe I have this issue resolved.  Thanks for the quick responses.


04-18-2016 18:44

Thanks Kristina-

I was looking for this and couldn't find it.  Indeed my terminology above was a bit sloppy.

The terms in the help are Relationship Status Indicator and the For Coverage option under Relationship Rules.  Thinking about the indicator as a Suspect flag belies the function.  In the first link there's a bullet list which lists the things that can trigger the indicator (and, I think, the item in a list view).


04-18-2016 18:19

Jodi, this topic is (briefly) addressed in a Relationship Rules article, so I've merged your topic. Short answer, no. Please reply if you need clarification on this after taking a look!

04-18-2016 18:18

This reply was created from a merged topic originally titled What function does "For Coverage" serve when setting up relationship rules?.

We are creating an Enterprise relationship rule set.  I need a better understanding of what selection "yes" for the "for coverage" option does outside of making the line solid in the diagram?  I can't seem to find much about this option in Jama's documentation.  Does this have some implication in the coverage explorer?

Jodi Koch

03-23-2016 02:22

Hi Bob,

Thanks for catching that! I made the correction. 

- Matt

03-18-2016 11:02

Hi Bob!

Thank you for pointing this out because there was a bit of an oversight on our part. The For Coverage option only toggles the orphan item flag for relationship fulfillment so, you would only enable this for required relationships. If items are related, they will always show in the Coverage Explorer, regardless of the For Coverage option.

Great catch!


03-08-2016 14:50

Hey Matt-

Nice run down!  One thing we came across recently is that it appears For Coverage has also is connected to what can be flagged as a suspect.  We selected this option thinking about traceability but that included some relationships we didn't want to cause Suspect flags.