Hi,

I am trying to use RTC as an offering to teams I work with trying to demonstrate an Agile concept, but I can't find a way to delete the demo project I created so that I can "go back" to before, and prepare for my next presentation.

I cannot use a VM snapshot, since this repository also serves my own development.

How can I delete an RTC project, and RTC workitem?

Thanks,

You can archive a project, but not delete it. Archived projects are hidden from you (unless you explcitly turn on options to include the archived projects). You will not be able to use the same name for the project as it is still there in the system - so Test001, Test002, etc become popular names for my test projects :-)


If you want to have a demo setup to show others, I recommend you have another RTC server instance (the standard tomcat/derby setup is the best). Then you can have a setup you can always reset (keeping a copy of the repositoryDB and workitems index directories in their initial state so you can restore the test server back to the beginning).

anthony

You cannot delete a project or a work item from a repository. You can
mark a project as "archived" which will hide it and its work items from
most GUI displays. For a work item, you can transition to some
appropriate "rejected" state, or you can just ignore it (because it is
in an archived project area, it won't show up in many displays).

Cheers,
Geoff

shaishap wrote:

Hi,

I am trying to use RTC as an offering to teams I work with trying to
demonstrate an Agile concept, but I can't find a way to delete the
demo project I created so that I can "go back" to before,
and prepare for my next presentation.

I cannot use a VM snapshot, since this repository also serves my own
development.

How can I delete an RTC project, and RTC workitem?

Thanks,

Just curious what the design rationale is for prohibiting users from deleting planned items.

I constantly have to "repurpose" the tasks and stories for my team by renaming them, and it's really time consuming, annoying, and frustrating.

Why do I have to do this? Because my whole team is new to RTC (who isn't?) and so we didn't know what we were doing when we first created our tasks/stories. We just jumped right in to that pretty interface... and now we are suffering because of it. :(

Also, I know there are a ton of other teams using RTC in agile development. Seems very un-agile-like to prevent users from deleting items... but maybe there is some logical explanation that I'm missing. Please enlighten me!

Thanks for listening!

Hello katie_thornton,

I am not on the dev team, but in some areas regulatories would not want you
to delete work items. Another to prevent from doing additional work by re
filing the same work item every half a year. A work item closed or rejected
is a design decision documented.

So, you should not have much work with work items that were put in accidentally.
Simply closing them and using sensible work item queries and filtering in
the plans should allow you to get rid of them.

Another way would be to move them to another project using the context menu
on a work item query that simply works as a dust bin.
If you want them out of the way you could also invent a type like "Deprecated"
and change the type of the WI's and close them. Again the work item queries
and other filters for rejected or otherwise closed work items come in handy.
I'd however suggest just to close them (as rejected if you have such a resolution).

On Jazz.net any user can create a work item and they can't delete them either.
I assume there are many work items coming in that might not be adressable
today but are kept for the future. Others are smply closed with some sensible
resolution (works as designed, rejected etc.)


Ralph

Just curious what the design rationale is for prohibiting users from
deleting planned items.

I constantly have to "repurpose" the tasks and stories for
my team by renaming them, and it's really time consuming, annoying,
and frustrating.
Why do I have to do this? Because my whole team is new to RTC (who
isn't?) and so we didn't know what we were doing when we first created
our tasks/stories. We just jumped right in to that pretty
interface... and now we are suffering because of it. :(

Also, I know there are a ton of other teams using RTC in agile
development. Seems very un-agile-like to prevent users from deleting
items... but maybe there is some logical explanation that I'm missing.
Please enlighten me!
Thanks for listening!