Hi Sawsan,
Thanks for adding that file. There are a few things to take a look at here:
-It looks like you have added two different item types to the template, UN and PR. The purpose of the CHILDREN table functionality is to display hierarchy (components/folders to what's inside of them). There isn't a way to mix item types using Word templates.
-To that end, the Upstream Relationships will display provided you keep those mail merge codes in the opening and closing tags for PRs.
So in order to display your PR in one column and their relationships in the next, you'd want to do something like
«TemplateStart:DEFAULTTEMPLATE»
«TemplateEnd:DEFAULTTEMPLATE»
«TemplateStart:PR»
«TableStart:HEADING»«name»«TableEnd:HEADING»
«description»
|
«TableStart:UPSTREAMRELATIONSHIPS»
«documentKey»
«name»
«traceDescription»
«TableEND:UPSTREAMRELATIONSHIPS»
|
«TemplateEnd:PR»
The attached document relationship_table includes this as written for Requirement types, but you can swap out that field code for the item key used in your instance. Any fields you want to include for the PR type should be in the left hand side of the column. You cannot configure additional fields for the upstream type, nor can you specify what item types are shown.
Let me know if this prompts more questions!
------------------------------
Kristina King
Jama Software
------------------------------
Original Message:
Sent: 01-16-2017 05:10
From: Sawsan Abusharkh
Subject: Export upstream relationships into a document
Hi Kristina,
Please find the attached template.
The idea to have the upstream relationships of each requirement in a column
«TableStart:CHILDREN:UN»
«documentKey»
|
«description»«TableEND:CHILDREN:UN»
|
«TableStart:CHILDREN:PR»
«documentKey»
|
«description»
|
upstream relationships
UR1, UR2, .....
|
«category»
«TableEND:CHILDREN:PR»
|
------------------------------
Sawsan Abusharkh
------------------------------
Original Message:
Sent: 01-03-2017 12:13
From: Kristina King
Subject: Export upstream relationships into a document
Hi Sawsan,
We have a defect filed for the report All Item Details not showing relationships (SOS-DEF-1067). This defect should be fixed in the next release of Jama, 8.12.
This defect should not be affecting your Word template, however. Can you attach a copy of your .doc template (not the export, just the template) so I can take a look and see if anything looks awry? There is not a setting that enables relationships to be exported in reports.
------------------------------
Kristina King
Jama Software
Original Message:
Sent: 01-02-2017 05:50
From: Sawsan Abusharkh
Subject: Export upstream relationships into a document
Hi Kristina,
Thank you very much for the reply. Actually I tried to insert the relationship merge mail, but no relationships are exported.
I also tried the default template:
Export --> office templates --> All item details
Then check the parameter "Include Relationships"
but also no relationships are shown in the exported document
Is there any configuration on the project level should be done to enable the relationships in the exported document?
------------------------------
Sawsan Abusharkh
Original Message:
Sent: 12-19-2016 16:11
From: Kristina King
Subject: Export upstream relationships into a document
Hi Sawsan,
You can add upstream relationships from your product requirements using the upstream mail merge code found on your field reference guide. It will look something like this:

The catch being you cannot specify what upstream item types it will show; in other words, you can't limit it to User Needs—you'll be exporting all items that are related upstream from the PRs.
If you need more on using tables in your word doc, check out this tutorial.
------------------------------
Kristina King
Jama Software
Original Message:
Sent: 12-19-2016 12:05
From: Sawsan Abusharkh
Subject: Export upstream relationships into a document
In the relationships rules, the product requirements are derived from user needs.
Let's say we have:
PR-XX that has two upstream User Needs UN1, UN2
How can I add a new column to the product requirements table in the exported office word document, that contains the list of all upstream needs.
For example:
ID | Product Requirement | Upstream |
PR-XX | product requirement description | UN1, UN2 |
------------------------------
Sawsan Abusharkh
------------------------------