We are aware of an issue causing intermittent login problems for some users following a recent update. Learn More
I have a customer requirement document that has the following format:
Heading 1
[Some description]
Heading 2
[Some description]
Heading 3
[Some description]
[requirementId-101] text description for requirement
[requirementId-102] text description for requirement
So when I import the document, I end up getting Heading 3 in its own requirement, which in this case it includes the description and the 2 requirements (Customer specification sometimes even has 10 of these requirements). So my question is, how can I import each [requirementId-XXX] into its own requirement in the tracker. Having too many requirements from the customer into a single requirement in Codebeamer is making it difficult to accurately track traceability.
The customer document is in Word and won't be sending us any intermediate files btw. And a side question... can the requirements not have a Summary?
Solved! Go to Solution.
Hello @RobSal ,
Codebeamer's import from Word is based on the heading styles.
After the import, the heading styles will be the summaries of the work items, and the paragraphs after the headings with normal styles will be the descriptions.
The different levels of heading styles will create the parent-child relations between the work items.
You can import only the summary and the description of the requirements, both needed for separate the items.
The summary can be empty if you set it to not mandatory, but for the import point of view it is required to identify the beginning of the new item.
You can find the details of this function in the Help Center: https://support.ptc.com/help/codebeamer/r2.1/en/index.html#page/codebeamer/user_guide/834055.html
Hello @RobSal ,
Codebeamer's import from Word is based on the heading styles.
After the import, the heading styles will be the summaries of the work items, and the paragraphs after the headings with normal styles will be the descriptions.
The different levels of heading styles will create the parent-child relations between the work items.
You can import only the summary and the description of the requirements, both needed for separate the items.
The summary can be empty if you set it to not mandatory, but for the import point of view it is required to identify the beginning of the new item.
You can find the details of this function in the Help Center: https://support.ptc.com/help/codebeamer/r2.1/en/index.html#page/codebeamer/user_guide/834055.html