Team Areas - delete

I don't think you can delete team areas from the gui. I believe you need to use some server-side API, but I haven't seen what that is. I haven't really looked for it either.

The reason you can't delete some objects I believe is to prevent people from accidentally deleting them. In a system like this, the only reason you would want to delete something is if you created it for testing or created it accidentally, and in those rare cases you don't need a fully-functional client in order to delete them; just use the special server api, whatever that is :-) Archiving them is more useful and allows for better record keeping.

In the Team Organization view (formerly, "Project Area Explorer") you
can right click on a team area and choose "Move..." to choose a new parent.

- Jared

bhadrim wrote:

Hi,

Is there a way to delete team areas? or Is there a way to associate
the team area to a parent after I create the Team Area?

I tried the context menu, did not find any option to perform the above
operations.

I noticed that certain objects cannot be deleted from Jazz system. Is
there a reason for this?

Thanks in advance.

Thanks for the replies. I found the Move option after I posted my query in the forum.

>>The reason you can't delete some objects I believe is to >>prevent people from accidentally deleting them.

Thanks for the information that there are APIs to delete the objects.

There are cases where I need to delete them. One that I can think of is the Users. If an user leaves the company or the development organisation, then I no longer need him in the system.

As mentioned in other threads we generally don't support the deletion of
items such as users, team areas, etc. The only real exception I am aware of
are build results.
The reasoning behind not allowing deletion is to protect the integrity of
the system.

Lets take the example of a user. A user has created and modified work items,
created and modified files etc. When looking at the history of these work
items for files you still want to know who made the changes; i.e. we cannot
physically delete the user. When somebody is no longer a member of a certain
team you remove this user from the appropriate team area. When you want to
avoid that a particular user makes changes to a jazz server or can read
items stored on the server, you need to remove the read and write system
permissions from that user.

For project and team areas we have the notion of marking them as inactive
(in the current version it is still called 'Archiving' but will be renamed
to 'Mark Inactive'). Inactive project and team areas can be filtered from
the UI. We plan to extend this notion to users and other items.

Cheers, Kai


"bhadrim" <bhadrim@ca.ibm-dot-com.no-spam.invalid> wrote in message
news:fakfg5$20t$3@localhost.localdomain...

The reason you can't delete some objects I believe is to
prevent people from accidentally deleting them.

Thanks for the information that there are APIs to delete the objects.


There are cases where I need to delete them. One that I can think of
is the Users. If an user leaves the company or the development
organisation, then I no longer need him in the system.

Thanks for the reply. If making an user inactive strips all his permissions that is what I am looking for.

As Kai mentioned, there is a capability to 'archive' Project Areas and Team Areas, which you can think of as a 'logical delete' while maintaining the integrity of existing references.

Re: user archiving, this capability is not yet in the system, but is a high-priority enhancement (WI 29896).