Entity Relationships

I have not used AgileTrack for some time now as I found it difficult to manage several independent projects. Recently, I was cleaning up the projects I had entered (deleting them) in order to start over and try to learn how to use the tool.

I had about 6 projects each with some releases, iterations, and issues. I deleted the projects and was surprised to find that nothing other than the project itself was deleted. All of the releases, iterations, and issues that were assigned to the project remained.

In order to delete all of the project artifacts I had to open each one and delete. I didn't want to waste my time deleting each and every artifact so I just dropped the schema and started over.

What is the purpose of leaving project artifacts around?

One of the problems I encountered initially was using my regular naming scheme for releases and iterations. When looking at the Releases tab it was impossible for me to tell which release belonged to which project. The same for iterations. I could look at the Issues tab and filter by project but this tab is more focused on Issues and not Releases and Iterations, IMO.

What I was expecting was a project view that allowed me to see all releases, iterations and issues for a single project.

How should I be using AgileTrack to manage multiple independent projects? What is a good naming scheme?