Creating a folder

About this task

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))]
-cus|-custom custom_query
Specifies to include the specified custom query expression in the new folder query.
-db|-dbid|-database_id database_spec...
When used with the -ts|-scope|-task_scope option, specifies a database identifier that modifies the query generated from the task scope. See Database specification for further details.
-mode ((man|manual) | (uq|use_query))
Specifies whether to add tasks to the new folder manually or by using a query.

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:

  • If you have defined a default_task_query, it is used.
  • If you haven’t defined a default query, the task scope All my assigned and completed tasks is used.
-n|-name folder_name
Specifies the name of the new folder to be created. The folder_name cannot contain newline characters.
-plat|-platform platform
Specifies that the task query for the folder will include a query for the specified platform.
-purpose purpose
Specifies to create the folder with a task query that includes a query for the specified purpose. See the project_purpose command Description and uses for a detailed description of purposes.

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.

-qu|-query
Specifies that the new folder will be query-based. This is synonymous with using
-mode use_query. See -mode ((man|manual) | (uq|use_query)) for details.
-q|-quiet
Specifies to show only the display name of the created folder. The display name shows a valid Folder specification.
-rel|-release release_spec
Specifies to create the folder with a task query that includes a query for the specified release. You can set the release_spec to multiple releases. See Release specification for further details.
-sub|-subsystem subsystem
Specifies to create the folder by using a task query that includes a query expression for task subsystem.
-ts|-scope|-task_scope
Specifies to use a task query. The task query will include a query expression that depends on the specified scope. The query expression associated with the specified scope also depends on the -database_id option. You can use the following scopes:
  • user_defined

    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.

  • all_my_assigned|all_owners_assigned

    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.

  • all_my_assigned_or_completed|all_owners_assigned_or_completed

    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.

  • all_my_completed|all_owners_completed

    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.

  • all_my_tasks|all_owners_tasks

    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.

  • all_completed

    This scope queries for all completed tasks. If you specify -database_id, the query is for all tasks completed in the specified database.

  • all_tasks

    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.

  • component_task_projects|component_task_products| component_task_projects_products

    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.

-w|-writable (owner | (build_mgr|build_manager|buildmanager) | all | none)
Specifies who can modify the new folder.

Examples

About this task

  • Create a new folder named Tested Tasks for Release 3.5 that is writable by its owner, and suppress all output from the command except for the folder ID.

    ccm folder -cr -n "Tested Tasks for Release 3.5" -w Owner -q 159

  • Create a new folder named My Tasks for Release 3.5 that uses a task_spec and a release value for a query_spec.

    ccm folder -cr -name "My Tasks for Release 3.5" -ts all_my_tasks -rel 3.5
    Created folder 160.


Feedback