Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic SYNERGY (steve huntington)
Decrease font size
Increase font size
Topic Title: Deleting Tsks
Topic Summary: Deleting empty tasks can be useful
Created On: 27-Jun-2005 19:44
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by Harold Vanderpool, on Thursday, June 30, 2005 6:50 PM

Answer:
Thanks
 27-Jun-2005 19:44
User is offline View Users Profile Print this message


Harold Vanderpool

Posts: 8
Joined: 23-Jun-2004

It would be convenient on occasion, to delete a task that exists. I understand that this is generally not a good CM practice, especially if the task has any object associated. However, we sometimes accumulate empty tasks for work that does not need to be done anymore and I would like to clean them up. The command reference suggests that

ccm delete /task

should work. I get an error that request a full object specification. My specific syntax while logged in as the owner (developer or buildMgr role) of the task is:

ccm delete /task 2005

and the error is:

"Object version specification required for 'delete'."

Thanks
Report this to a Moderator Report this to a Moderator
 28-Jun-2005 10:00
User is offline View Users Profile Print this message


Toni Arte

Posts: 30
Joined: 16-Aug-2004

quote:

Originally posted by: Harold Vanderpool
It would be convenient on occasion, to delete a task that exists. I understand that this is generally not a good CM practice, especially if the task has any object associated. However, we sometimes accumulate empty tasks for work that does not need to be done anymore and I would like to clean them up.


It is possible to re-use the 'task_assigned' task, as all task relations and attributes (except the task number) are modifiable. So use the same task for something else, just disassociate all old objects (if any), and modify the 'release', 'task_synopsis' etc. fields.

If you really want to delete the 'task_assigned' task, yes that is possible and IMHO not against good CM practices. 'completed' tasks should not be deleted, though. Any developer can delete their 'task_assigned' tasks:

ccm query -n task123
ccm delete @1
--
Toni

Report this to a Moderator Report this to a Moderator
 29-Jun-2005 04:33
User is offline View Users Profile Print this message


Vincent Gaudeul

Posts: 68
Joined: 10-Oct-2002

Hello,

the "ccm delete /task" command cannot be used to delete a task. ccm delete /task is used to delete any object (file or directory). Task information will be used if a new version of parent directory must be automatically checked-out during "ccm delete" operation.

So actually, "ccm delete /task" command requires a task number AND an object specification. For example:

ccm delete /task 34 foo.c-1:csrc:M

I fully agree with Toni: it may be useful to delete "task_assigned" tasks using a "ccm query", then a "ccm delete" command, even if it may be easier to re-use existing non-completed tasks, or moving them to a GARBAGE release tag, which would be cleaned every night for example by a scheduled script.

Vincent
Report this to a Moderator Report this to a Moderator
 30-Jun-2005 18:50
User is offline View Users Profile Print this message


Harold Vanderpool

Posts: 8
Joined: 23-Jun-2004

Answer Answer
Thanks
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic SYNERGY forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 15:34.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.