-
Bug
-
Resolution: Fixed
-
Low
-
10.125.2
-
1
-
Severity 3 - Minor
-
No
Issue Summary
When a feature has a theme assignment changed via import, the change does not apply to all data in the feature's details.
Steps to Reproduce
- Have a Feature A
- Linked to Epic A
- Linked to Theme A
- Linked to Epic A
- Have a Feature B
- Linked to Epic B
- Linked to Theme B
- Linked to Epic B
- Edit and Export Feature B so it links to the Theme A
- Import the feature to apply the change
The new hierarchy should be:
- Theme A
- Epic A
- Feature A
- Feature B
- Epic A
- Theme B
- Epic B
- none
- Epic B
Expected Results
The data should show the updated theme across the board, including
- Grid columns
- Feature's details
- Filters
- Requirement Hierarchy
- Export
- etc...
Actual Results
In Feature grid, the column for Theme shows Epic the correct new assignment,
- Feature A = Theme A
- Feature B = Theme A
The export function shows the correct result
- Theme A
- Children : Epic A + Feature A + Feature B
- Theme B
- Children : Epic B
- Theme A
The filters also apply in the same fashion
Feature A and B shows if filter is set to Theme A
Feature B shows if filter is set to Theme B
The Feature's details panel show incorrect Theme assignment
- Feature A show like to Theme A
- Feature B show link to Theme B
Requirement Hierarchy Shows the incorrect Assignment as well
- Theme A
- Epic A
- Feature A
- Epic A
- Theme B
- Epic B
- Feature B
- Epic B
- Theme A
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- resolves
-
ALIGNSP-20693 Loading...