![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: How can I delete Change Requests? Topic Summary: Created On: 8-Jul-2003 12:14 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: replace the smiley by ":" and "p" (the forum editor replace these letters by a smiley :-( ) Note: when you do the query you can format output with -f "%objectname" to get CR unique identifiers. | |
![]() |
|
We have our first set of users on the system. They started off entering test Change Requests before entering any live ones. They now want the 'test' ones deleted but I can't see how to delete them.
Anyone know how? |
|
![]() |
|
![]() |
|
On command line as pt_admin or ccm_admin role:
ccm query -t problem ...... ccm delete @entrynum or ccm delete objectname objectname for CR is problemXXX~1 ![]() ------------------------- Pierre Guillet |
|
![]() |
|
![]() |
|
What's the objectname for a CR?
The last reply has a 'smiley face' in the middle of problemXXX~1roblem:YYY ! |
|
![]() |
|
![]() |
|
replace the smiley by ":" and "p" (the forum editor replace these letters by a smiley :-( ) Note: when you do the query you can format output with -f "%objectname" to get CR unique identifiers. ------------------------- Pierre Guillet |
|
![]() |
|
![]() |
|
Here is an answer from Telelogic support (from a Techinal Bulletin ?):
Question 2.2) How can I set the next problem or task number to some arbitrary number? The next problem and next task numbers are both attributes stored on an administrative object in a CCM database. The attribute can be modified with the attribute command as follows: To change the next problem number: # query for the admin object (one object should be returned) # then set the next_problem attribute to some value, say 6000 % ccm query -name probtrac_seed -type admin % ccm attr -m next_problem -v 6000 @1 To change the next task number: # query for the probtrac_seed object (one object should be returned) # then set the next_task attribute to some value, say 3578 % ccm query -name probtrac_seed -type admin % ccm attr -m next_task -v 3578 @1 Note: Care should be taken when setting the problem or task number so that the value is never the same as an existing problem or task. If the value is set to a value that is lower than an existing problem or task then at some point in the future these numbers may overlap. Attempts made to create a problem or task with a number that already exits will fail and the information will be lost. ------------------------- Pierre Guillet |
|
![]() |
|
![]() |
|
From my point of view, filling in existing gaps in problem numbering may be dangerous.
How could you distinguish a problem #123 (Defect) that was submitted one week ago on product A from another problem #123 (Defect) submitted yesterday on product B after 'old' problem #123 had been deleted ?? It can be very confusing for users to fill in gaps in problem numbering, especially in a production database. Vincent |
|
![]() |
|
![]() |
|
I wasn't bothered about the existence of gaps in the numbering.
As far as I'm concerned, one should attach meaning to the other fields in a Change Request or Task - the number is just a unique identifier Hugh |
|
![]() |
Telelogic SYNERGY
» SYNERGY/Change
»
How can I delete Change Requests?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.