This subcommand creates a folder.
When you use an option more than once, the query expression relating to each usage is combined with an "or". For example, if you specify -release 1.0 -release 2.0, this contributes a query expression of (release='1.0' or release='2.0).
Contributions from different options are combined with "and". For example, if you specify -release 1.0 -platform windows, this contributes a query expression of (release='1.0') and (platform='windows').
ccm folder -cr|-create -n|-name folder_name ([-qu|-query] | [-mode ((man|manual) | (uq|use_query))]) [-w|-writable (owner | (build_mgr|build_manager|buildmanager) | all | none)] [-q|-quiet] [-cus|-custom custom_query] [(-db|-dbid|-database_id database_spec)...] [(-plat|-platform platform)...] [(-purpose purpose)...] [(-rel|-release release_spec)...] [(-sub|-subsystem subsystem)...] [-ts|-scope|-task_scope (user_defined | (all_my_assigned|all_owners_assigned) | (all_my_assigned_or_completed|all_owners_assigned_or_completed) | (all_my_completed|all_owners_completed) | (all_my_tasks|all_owners_tasks) | all_completed | all_tasks)] (ct_projs|ct_projects|component_task_projects) | (ct_prods|ct_products|component_task_products) | (ct_projs_prods|ct_projects_products | component_task_projects_products))]
If you don’t specify -mode or -query, the default mode depends on whether you specify query-related options. If you specify -custom, -dbid, -platform, -release,
-subsystem, -task_scope, the default mode is query-based. If you don’t specify any of these options, the default is to add tasks to the folder manually.
If you specify -mode use_query or -query, but don’t specify -custom, -dbid,
-platform, -release, -subsystem, or -task_scope, a default task query is used in this way:
This option typically applies to queries for component tasks that are specified with one of these scopes: component_task_projects, component_task_products, or component_task_projects_products.
This scope is defined by the default_task_query option. If you specify
-database_id, the query also includes a query expression for tasks modifiable in or completed in the specified database.
This scope queries for all tasks assigned to you. If you specify -database_id, the query is for all tasks assigned to you that are modifiable in the specified database.
This scope queries for all tasks assigned to you or completed by you. If you specify -database_id, the query is for all tasks assigned to you and modifiable in the specified database, or completed by you in the specified database.
This scope queries for all tasks completed by you. If you specify -database_id, the query is for all tasks completed by you in the specified database.
This scope queries for all tasks for which you are the task resolver. If you specify -database_id, the query is for all tasks for which you are the task resolver and that are modifiable in the specified database or were completed in the specified database.
This scope queries for all completed tasks. If you specify -database_id, the query is for all tasks completed in the specified database.
This scope queries for all tasks. If you specify -database_id, the query is for all tasks that are modifiable in the specified database or that were completed in the specified database.
This scope queries for component tasks for projects, products, or projects and products. If you specify -database_id, the query is for all component tasks that were created in the specified database. If you specify -purpose, the query is for component tasks with the specified purpose.
ccm folder -cr -n "Tested Tasks for Release 3.5" -w Owner -q 159
ccm folder -cr -name "My Tasks for Release 3.5" -ts all_my_tasks -rel 3.5
Created folder 160.