![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Move non-completed tasks to next release? Topic Summary: Created On: 2-Aug-2004 19:50 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Thanks all, I got it....I read the manual! (they don't have an embarassed smiley) I did the following: ccm query "(type='task') and (((release='4.3') and not (status='completed')) or (release='4.4'))" ccm task -modify -release 4.4 @ Then I did the following to change the automatic tasks back to 4.3: ccm query "(type='task') and (release='4.4') and (status='task_automatic')" ccm task -modify -release 4.3 @ Now I won't forget! Thanks again, Lorin | |
![]() |
|
Hi,
I am fairly new at this, and need to move about 248 non-completed tasks from release 4.3 to release 4.4. Is there a easy way to do this other than individually as ccm_root? Thanks, Lorin |
|
![]() |
|
![]() |
|
You can do this from the command line. First query for the non-completed tasks (make sure to omit automatic tasks). Then use the ccm attr command to modify the release value of all the tasks (specify "@" as the object argument for the ccm attr command). From the command line, a build_mgr should be able to do this.
|
|
![]() |
|
![]() |
|
Thanks for the info, but what are automatic tasks, and how do I find out if I have any?
Just before I got your reply, I did this: ccm query "(type='task') and ((release='4.3') and not (status='completed'))" ccm task -modify -release 4.4 @ Which doesn't omit automatic tasks. I should have waited an hour more! Is this a problem? Lorin |
|
![]() |
|
![]() |
|
Hi Lorin,
"automatic tasks" are created by CMS itself, usually based on actual release value, project purpose and/or owner. The collect "product" objects and "project" object (in order to keep track of subprojects). You can taek a look at these tasks by switching "show automatic tasks" in the projects reconfigure properties. You may query for objects with status task_automatic, too. regards, Mert |
|
![]() |
|
![]() |
|
Thanks all,
I got it....I read the manual! (they don't have an embarassed smiley) I did the following: ccm query "(type='task') and (((release='4.3') and not (status='completed')) or (release='4.4'))" ccm task -modify -release 4.4 @ Then I did the following to change the automatic tasks back to 4.3: ccm query "(type='task') and (release='4.4') and (status='task_automatic')" ccm task -modify -release 4.3 @ Now I won't forget! Thanks again, Lorin |
|
![]() |
|
![]() |
|
Hmmm,
Are you sure that changing the task release is suffisant ? may the release of the associated objets be changed too ? I created a windows script to change the task and associated objects : @echo off if "%1"=="" goto usage if "%2"=="" goto usage ccm delim >cmqry00.txt FOR /F "delims=" %%I IN (cmqry00.txt) DO set delimiteur=%%I set tache=task%2 ccm query -n %tache% >NULL: if "%errorlevel%"=="0" goto verif_release echo. echo La tache specifiee est introuvable ! goto fin :verif_release ccm release -l >cmqry.txt FOR /F "delims=:" %%I IN (cmqry.txt) DO if "%%I"=="%1" goto rechercher echo. echo La release specifiee est inexistante ! goto fin :rechercher echo. echo ---------------------------------------------------------------------- ccm query -n %tache% -f "%%name %%release" -u echo ---------------------------------------------------------------------- ccm query is_associated_object_of('%tache%%delimiteur%1:task ![]() echo ---------------------------------------------------------------------- echo. choice Etes-vous sur de vouloir changer la release de la tache %2 et ses objets associes en %1 ? /c ![]() if errorlevel 2 goto stopper if errorlevel 1 goto executer :executer ccm query -n %tache% >NULL: ccm attr -m release -v %1 @1 >NULL: ccm query is_associated_object_of('%tache%%delimiteur%1:task ![]() ccm attr -m release -v %1 @ >NULL: echo. echo Changement de release en %1 effectue avec succes. goto fin :stopper echo. echo Operation de changement de release stoppee ?? goto fin :usage echo. echo CHANGE_RELEASE v2.0 echo Change la release d'une tache avec tous ses objets associes echo. echo Usage: change_release [numero_nouvelle_release] [numero_tache] echo. goto fin :fin if exist cmqry00.txt del cmqry00.txt if exist cmqry.txt del cmqry.txt Hope help you by this remark, Lyes GUERROUI Lotsys France. |
|
![]() |
|
![]() |
|
FYI, you may change the release value on the associated objects, but it is not necessary. It is the task's release value that is used by reconfigure.
If I rmeember correctly, since the objects are static, you must be ccm_admin to change the release value on the objects. This being the case, I reccommend against changing the object's release value. IMHO, you want to do as few operations as ccm_admin as possible, and should restrict the ccm_admin role to only those that truely need to admin the system (not build managers). This is one of the best ways to keep your data safe and your users out of trouble. Edited: 4-Aug-2004 at 13:22 by Todd Alden |
|
![]() |
Telelogic SYNERGY
» SYNERGY/CM
»
Move non-completed tasks to next release?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.