PUT/projects/{ProjectId}/{EntityCode}/folders/{Id}

Applies to QAComplete 12.70 SaaS, last modified on January 11, 2021

Updates the specified folder.

Use the operation to replace the existing content of the folder’s fields with new content in QAComplete.

To update individual fields of a folder, use the …/{EntityCode}/folders/{Id} (PATCH) operation. To add a new folder, use the …/{EntityCode}/folders (POST) operation.

Authentication

Basic authentication using a user’s login and password. See Authentication for details.

Security Rights

The authenticating user must belong to a security group that has the Update privilege for the specified entity type.

Request Format

To update the folder, send a PUT request to the following URL:

http://{server}/rest-api/service/api/v2/projects/{ProjectId}/{EntityCode}/folders/{Id}
URL parameters

ProjectId  :  integer, required

The ID of the project, which folder you need to update.

EntityCode  :  string, required

The entity, which folder you need to update. Possible values:

  • Releases
  • Bugs (defects)
  • FunctionalSpecs (requirements)
  • Tests
  • TestSets
  • TestSteps

Id  :  integer, required

The ID of the folder you need to update.

Body parameters

In the request body, pass the RequestFolderPut JSON object that describes new contents of the folder:


{
  "FolderName": "string",
  "Description": "string",
  "IsPublic": "boolean",
  "ParentName": "string",
  "IsActive": "boolean"
}

The property values you do not specify are set to their default values.

FolderName  :  string, required

The folder’s name.

Description  :  string

The short description of the folder.

IsPublic  :  boolean

Defines whether the folder is public or private.

ParentName  :  string

The parent folder’s name.

IsActive  :  boolean

Defines whether the folder is active or hidden.

A sample request:

PUT http://yourserver.com/rest-api/service/api/v2/projects/11873/FunctionalSpecs/folders/77 HTTP/1.1
Host: yourserver.com
Connection: keep-alive
Content-Type: application/json
Accept: application/json
Authorization: Basic am9obkBleGFtcGxlLmNvbTpwQHNzd29yZA==
Content-Length: 218


{
  "FolderName": "Sample Folder",
  "Description": "This folder’s description and availability will be changed after this request.",
  "IsPublic": false,
  "IsActive": true
}

A sample request made by using cURL:

curl -u john@example.com:p@ssword -d @folder.txt -H "Content-Type: application/json" -H "Accept: application/json" http://yourserver.com/service/api/v2/projects/11873/FunctionalSpecs/folders/88

Response Format

If successful, the operation responds with HTTP status code 200. The response is a JSON object with the updated folder information.

A sample response:

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 577



   {
  "id": 77,
  "parent_id": 0,
  "project_id": 11873,
  "entity_code": "Requirements",
  "folder_name": "Sample Folder",
  "description: "This folder’s description and availability will be changed after this request.",
  "is_active": true,
  "is_public": false,
  "date_created": "2013-09-14T13:53:53.4230000",
  "date_updated": "2013-09-14T13:53:53.4230000",
  "update_user_id": 24663,
  "owner_user_id": 24663,
  "full_folder_name": "Sample Folder",
  "updated_user_name": "Smith, John",
  "created_user_name": "Smith, John"
   }

Error responses

If the operation fails, it returns the appropriate status code and (optionally) the error description in the response body.

If the project with the specified ProjectId does not exist or the authenticating user does not have rights to access the project, the operation returns the Access is denied error.

If the specified entity does not exist, the operation returns the 'Invalid entity code' error.

See Also

Folders REST API Reference

Highlight search results