Issue with component hierarchy in Create Issue and Issue Filter
I am evaluating Gemini for use in our organization, and as such I have started to create a project that is similar to our existing projects in Mantis.
The project is called R3.4, and I have created some components for the project in this tree structure:
- R3.4
- R3.4 Data Synchronization
- R3.4 Scheduler
- R3.4 Subscriber Data Management
- R3.4 Web Application
- R3.4 Activity
- R3.4 Subscriber Management
- R3.4 Subscriber Account
- R3.4 Subscriber Offices
When I view the components for the project (Projects | R3.4 | Components), the Component Maintenance tree view shows it correctly as I have illustrated above. However, when I go to create an issue, the "Component Affected" field shows the tree like this:
- R3.4 Data Synchronization
- R3.4 Scheduler
- R3.4 Subscriber Data Management
- R3.4 Subscriber Account
- R3.4 Subscriber Offices
- R3.4 Web Application
- R3.4 Activity
- R3.4 Subscriber Management
The "R3.4 Subscriber Account" and "R3.4 Subscriber Offices" components are listed with the wrong parent. I assume it is because the name is similar? Shouldn't it be using the ID for the parent and not the name? When I query the GeminiSample database, the "R3.4 Subscriber Account" and "R3.4 Subscriber Offices" components do show the correct parent ID in GEMINI_COMPONENTS.parentcomponentid.
This incorrect hierarchy is also reflected in the Issue Filter, Component field when I view the R3.4 project.
swhalen
· 1 |
|
Thursday, January 15, 2009, 5:13:27 PM |