Gets information on a requirement from QAComplete.
Use the operation to get information on a requirement specified by its ID.
To get information on all the requirements registered in a QAComplete project, use the
…/requirements (GET) operation.
Basic authentication using a user’s login and password. See Authentication for details.
The authenticating user must belong to a security group that has the Read privilege for Requirements.
To get information on a requirements, send a GET request to the following URL:
ProjectId : integer, required
The ID of the project, to which the requirement belongs.
Id : integer, required
The ID of the requirement you want to get.
A sample request:
GET http://yourserver.com/rest-api/service/api/v1/projects/11873/requirements/1 HTTP/1.1
Authorization: Basic am9obkBleGFtcGxlLmNvbTpwQHNzd29yZA==
A sample request made by using cURL:
curl -u email@example.com:p@ssword -H "Accept: application/json" http://yourserver.com/service/api/v1/projects/11873/requirements/1
On success, the operation responds with HTTP status code 200 and returns a JSON object with the requirement information.
A sample response:
HTTP/1.1 200 OK
"title": "Add Visual Studio Integration",
"assigned_to_name": "Smith, John",
"comments": "comment 1",
"description": "Add integration with Microsoft Visual Studio",
"notes_description": "note 1",
"opened_by_name": "Smith, John",
"owner_name": "Smith, John",
"user_name": "Smith, John"
The authenticating user’s rights to access requirements.
- 0 - None
- 1 - Read
- 2 - Update
- 3 - Read and update
- 4 - Delete
- 5 - Read and delete
- 7 - Full access
Unique identifier of the requirement.
The ID of the QAComplete project that contains the requirement.
The requirement title (name).
The requirement status based on a choice list.
Specifies whether the requirement is enabled (active).
Keywords of the requirement.
The group that contains the requirement.
The sub group that contains the requirement.
Long description of the requirement. Can include HTML markup.
Business rule associated with the requirement. Can include HTML markup.
Estimated hours to finish the requirement.
Estimated start date for working on the requirement.
The estimate date of the finishing the requirement.
Actual hours spent working on the requirement.
Actual start date for working on the requirement.
The actual date when the requirement was completed.
The date and time when the requirement was last updated.
The date and time when the requirement was created.
The date and time when the requirement was opened.
The ID of the last user who updated the requirement.
For importing: the original key that was imported.
The ID of the import session, in which the requirement was imported. If the requirement was created in QAComplete, the ImportId property is equal to 0.
The ID of the user who owns the requirement.
The ID of the user the requirement is assigned to, or 0 if the requirement is not assigned to anyone.
The ID of the folder containing the requirement, or 0 if the requirement is not in any folder.
Percentage complete of requirement completing.
Estimated remaining hours for finishing the requirement.
The ID of the user who opened the requirement.
The name of the last user who updated the requirement, in the Lastname, Firstname format.
The name of the user who owns the requirement, in the Lastname, Firstname format.
The name of the user to whom the requirement is assigned, in the Lastname, Firstname format.
The latest note attached to the requirement. Can include HTML markup.
The number of files attached to the requirement.
The number of notes attached to the requirement.
The number of scheduled events associated with the requirement.
The number of tasks linked to the requirement.
The name of the folder containing the requirement, in the format ParentFolder/Subfolder/Subfolder.
The name of the user who opened the requirement, in the Lastname, Firstname format.
The e-mail address of the user who registered the requirement.
The company name of the user who registered the requirement.
The number of times the requirement was processed by escalation rules.
The date when the requirement was last processed by an escalation rule.
The ID of the escalation rule that processed the requirement last. 0 if no escalation rule processed the requirement.
The name of the escalation rule that processed the requirement last.
An array of objects that describe custom fields and their values.
Comments to the requirement. Can include HTML markup.
The unique identifier of a custom field.
The field name.
The field value.
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 requirement with the specified Id does not exist, the operation returns the
File or directory not found error.