Support

Most of a type of item in my instance of Jama were sourced from JIRA via Tasktop.  Most, if not all, of the items have the relationship status, "Missing Downstream, Orphan Item".  Looking at the downstream items in Jama, I don't see an issue.  They also exist in Jama and appear to match the originating relationship from JIRA.  Is this really an issue (that is, can it cause other issues such as synchronization problems), and if so, how can I determine the root cause for this indication?

------------------------------
Terry Williams
FLYHT, Inc.
------------------------------

Hi Terry,

Sorry you're running into this. Can you send over a screenshot of the error? I have a feeling this may be an existing bug, but I want to make sure first.

------------------------------
Kimberly Embry
------------------------------

Original Message:
Sent: 03-07-2018 13:53
From: Terry Williams
Subject: Relationship Status: Missing Downstream Orphan Item

Most of a type of item in my instance of Jama were sourced from JIRA via Tasktop.  Most, if not all, of the items have the relationship status, "Missing Downstream, Orphan Item".  Looking at the downstream items in Jama, I don't see an issue.  They also exist in Jama and appear to match the originating relationship from JIRA.  Is this really an issue (that is, can it cause other issues such as synchronization problems), and if so, how can I determine the root cause for this indication?

------------------------------
Terry Williams
FLYHT, Inc.
------------------------------

I'm having what sounds like the same issue, although not arising from a Jira import.

The Relationship Status column of my Requirements Set shows a Missing Downstream flag against each requirement (see top screenshot). A randomly selected requirement, when opened, shows 1 up (grey) /1 down (red) on the Relationship Status Indicator, and lists both upstream and downstream items in the Relationships pane (see bottom screenshot).

Only the Requirements with "not applicable" in the Verification Method column should show no downstream relationships (they contain design guidance or definitions referred to elsewhere in the Set).

There are no Suspect Links in the project.




Edited to add screenshot showing mouseover text:

I eventually solved the problem by tweaking the relationship rules. What I thought were parallel downstream items were actually both required in order to clear the flag.

------------------------------
.
------------------------------

Original Message:
Sent: 07-10-2018 21:40
From: Em R
Subject: Relationship Status: Missing Downstream Orphan Item

I'm having what sounds like the same issue, although not arising from a Jira import.

The Relationship Status column of my Requirements Set shows a Missing Downstream flag against each requirement (see top screenshot). A randomly selected requirement, when opened, shows 1 up (grey) /1 down (red) on the Relationship Status Indicator, and lists both upstream and downstream items in the Relationships pane (see bottom screenshot).

Only the Requirements with "not applicable" in the Verification Method column should show no downstream relationships (they contain design guidance or definitions referred to elsewhere in the Set).

There are no Suspect Links in the project.




Edited to add screenshot showing mouseover text:

Hey Em,

Thanks for following up and clarifying that you were able to resolve this and explaining what was going on.  Well done figuring that one out!

------------------------------
Nick S
Jama Software
------------------------------

Original Message:
Sent: 07-13-2018 00:53
From: Em R
Subject: Relationship Status: Missing Downstream Orphan Item

I eventually solved the problem by tweaking the relationship rules. What I thought were parallel downstream items were actually both required in order to clear the flag.

------------------------------
.

Original Message:
Sent: 07-10-2018 21:40
From: Em R
Subject: Relationship Status: Missing Downstream Orphan Item

I'm having what sounds like the same issue, although not arising from a Jira import.

The Relationship Status column of my Requirements Set shows a Missing Downstream flag against each requirement (see top screenshot). A randomly selected requirement, when opened, shows 1 up (grey) /1 down (red) on the Relationship Status Indicator, and lists both upstream and downstream items in the Relationships pane (see bottom screenshot).

Only the Requirements with "not applicable" in the Verification Method column should show no downstream relationships (they contain design guidance or definitions referred to elsewhere in the Set).

There are no Suspect Links in the project.




Edited to add screenshot showing mouseover text: