#99: Componets cannot have the same name
Issue revisions
- new by Markus at 2009-O-28 11:11
- new by Kore Nordmann at 2009-N-09 9:22
- assigned by Kore Nordmann at 2009-N-12 9:56
- assigned by Kore Nordmann at 2010-M-28 19:37
- closed by Kore Nordmann at 2010-M-28 19:37
| Type | |
|---|---|
| State | |
| Priority | |
| Resolution | |
| Assigned to | Kore Nordmann |
| Scheduled for | 0.3-alpha |
| Affected versions | Latest SVN |
| Affected components | Modules / Tracker |
| Last change | Sunday 28 March 2010 19:37:42 UTC by Kore Nordmann |
Short description
Components can be organized hierarchically, but you can't have two subcomponents with the same name:
-
Main component 1
-
Subcomponent
-
-
Main component 2
-
Subcomponent
-
Subcomponents with the same name can be stored via the admin interface, but when one of them is assigned to an issue and you access the issue later on, all subcomponents with the same name are selected in the issue form - the hierarchy is ignored.
Environment
PHP 5.3.0, Ubuntu 9.04, CouchDB 0.9.1
Steps to reproduce
-
Register two components or subcomponents with the same name
-
Create an issue, assign only one of the components
-
Reload the issue, go to "change issue status"
-
Look at the selectbox "affected components"
Expected behavior
Only the initially assigned component should be selected.
Actual behavior
All components with the same name are selected, regardless of hierarchy.
Kore Nordmann at Monday 9 November 2009 09:22:12 UTC
Scheduled for 0.3-alpha.
Kore Nordmann at Sunday 28 March 2010 19:37:10 UTC
Fixed in revision #1666.
Kore Nordmann at Sunday 28 March 2010 19:37:42 UTC
Actually close the issue…