Hi Rob,
Thanks for your valuable information. I am now able to pull linked items that are associated with requirement. But the problem I have is, it is creating separate building block for each linked item whereas I expected that it would generate one block for Requirement and linked items within that block as sub-section. The "Requirements Specification" layout which you have said generates test case as sub-item but it doesn't populate all the information I wanted to see.
How can I develop a custom report same as what "Requirements Specification" layout is doing but in presentable way to client.
For eg:
My custom report layout is as below
[
TFS ID: ID
TITLE - CLICK HERE TO ENTER TEXT.
[
TFS ID: 1234
TITLE - Test Requirement
Area Path: TFS\Requirements
Requirement Type: Functional
Priority: 1
Work Item Type: Requirement
Description:
[
TFS ID: 1212
TITLE - Test Case for TFS4WORD addin
Area Path: TFS\Requirements
Requirement Type: Requirement Type
Priority: 1
Work Item Type: Test Case
Description:
But the way I wanted to customize is as follows
[
TFS ID: 1234
TITLE - Test Requirement
Area Path: TFS\Requirements
Requirement Type: Functional
Priority: 1
Work Item Type: Requirement
Description:
Description
Thanks for your valuable information. I am now able to pull linked items that are associated with requirement. But the problem I have is, it is creating separate building block for each linked item whereas I expected that it would generate one block for Requirement and linked items within that block as sub-section. The "Requirements Specification" layout which you have said generates test case as sub-item but it doesn't populate all the information I wanted to see.
How can I develop a custom report same as what "Requirements Specification" layout is doing but in presentable way to client.
For eg:
My custom report layout is as below
[
TFS ID: ID
TITLE - CLICK HERE TO ENTER TEXT.
- Area Path: Area Path
- Requirement Type: Requirement Type
- Priority: Priority
- Work Item Type: Work Item Type
-
Description:
Description
-
STEPS:
CREATED ON CLICK HERE TO ENTER A DATE. BY CLICK HERE TO ENTER TEXT.Steps
]
[
TFS ID: 1234
TITLE - Test Requirement
Area Path: TFS\Requirements
Requirement Type: Functional
Priority: 1
Work Item Type: Requirement
Description:
Description
STEPS: Steps
CREATED ON CLICK HERE TO ENTER A DATE. BY CLICK HERE TO ENTER TEXT.
][
TFS ID: 1212
TITLE - Test Case for TFS4WORD addin
Area Path: TFS\Requirements
Requirement Type: Requirement Type
Priority: 1
Work Item Type: Test Case
Description:
Description
STEPS: 1. Step1 validating test action. Test action passed
2. Step2 Add testcase to word. Testcase added.
CREATED ON CLICK HERE TO ENTER A DATE. BY CLICK HERE TO ENTER TEXT.
]But the way I wanted to customize is as follows
[
TFS ID: 1234
TITLE - Test Requirement
Area Path: TFS\Requirements
Requirement Type: Functional
Priority: 1
Work Item Type: Requirement
Description:
Description
- Linked Items:
Test Case 1212 - Test Case for TFS4WORD addin
Status: Failed Priority: 2
Error Message: Separate blocks are generated for each work item.
Description:
Description
STEPS:
CREATED ON CLICK HERE TO ENTER A DATE. BY CLICK HERE TO ENTER TEXT.1. Step1 validating test action. Test action passed 2. Step2 Add testcase to word. Testcase added.
]