Hi "guy",
who deletes "music" from the component list?

Stefan
I'll maintain this.
It's easy to do... tedious, but easy.
louis

Tje initial issue is still open.
This was only a reminder that testing project creation leads to the
mentioned problem also.

I have just spoken to our lead IssueZilla developer. This is the 
correct and expected behavior of SourceCast - the idea is that 
the project space is created automatically at project _suggest_ 
so that work can begin, even if an admin later denies the project.

What's broken is that denial of the project deletes the project 
space - but not the IssueZilla component. This is an artefact of 
the OpenOffice IssueZilla database structure. It functions 
correctly in the core product (which uses a separate database 
for each project) but not on openoffice (for which all projects 
share a single issuezilla database).

This is not trivial to fix, so it is going to take some time. 
Meanwhile, this is more an annoyance than anything else. Louis 
will monitor the components list and delete as necessary. I will 
have a better idea for a schedule for completion in a week or so.

reassigned

Hi,

As stated by Jeff previously, the component not being deleted at
project deletion is a result of OpenOffice Issuezilla operating in
single database mode. 
There is no reliable method for verifying that the component creation
was the result of a project being created, and therefore should be
removed when the project is removed. Also, whether all the issues
associated with a component should in fact be deleted is in question
and could be hazardous in this situation if a component with the same
name as a project, but not in fact associated with that project,
exists.

This will not be addressed by the upgrade. The current workaround of
hand maintaining the components of issuezilla will remain. There are
alternatives to be considered for future upgrades:

1. switch to multi-database mode where this feature is implemented 

2. submit a request to have a feature added which would remove the
component and all issues associated with it corresponding to a deleted
project name. Understood in this will be that there is no reliable
method of checking that the component was in fact created as a result
of the project creation and that all associated issues will be removed
from the database.

My point is that creation of the IZ component before the project
approval leads to additional manual work during disapproval. For me
creation of IZ component should happen at approval time, but I
understand that you won't change this.

Suggestion 2 (delete all bugs and remove component) may lead to
improper deletions. A better solution could be to delete the component
only if it has no bugs. This still means that a manual check of the
component is needed.

Conclusion: no further action needed if you stick with the "expected
behavior" during project creation. Please comment and close.

We are still looking into a solution to this issue that may be more
suitable, however this is not on the immediate horizon. I will update
this issue as more information becomes available.