Get a list of available fields for epic tasks.api.scrum.epic.getFields
Scope:
taskWho can execute the method: any user
The method tasks.api.scrum.epic.getFields returns the available fields for an epic.
No parameters.
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-d '{
}' \
https://your-domain.bitrix24.com/rest/_USER_ID_/_CODE_/tasks.api.scrum.epic.getFields
curl -X POST \
-H "Content-Type: application/json" \
-d '{
auth=YOUR_ACCESS_TOKEN
}' \
https://your-domain.bitrix24.com/rest/tasks.api.scrum.epic.getFields
try
{
const response = await $b24.callMethod(
'tasks.api.scrum.epic.getFields',
{}
);
const result = response.getData().result;
console.log(result);
}
catch( error )
{
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'tasks.api.scrum.epic.getFields',
[]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error getting epic fields: ' . $e->getMessage();
}
BX24.callMethod(
'tasks.api.scrum.epic.getFields',
{},
function(res)
{
console.log(res);
}
);
require_once('crest.php'); // connecting CRest PHP SDK
// executing a request to the REST API
$result = CRest::call(
'tasks.api.scrum.epic.getFields',
[]
);
// Processing the response from Bitrix24
if ($result['error']) {
echo 'Error: '.$result['error_description'];
}
else {
print_r($result['result']);
}
Response Handling
HTTP status: 400
{
"fields":
{
"name": {
"type": "string"
},
"description": {
"type": "string"
},
"groupId": {
"type": "integer"
},
"color": {
"type": "string"
},
"files": {
"type": "array"
},
"createdBy": {
"type": "integer"
},
"modifiedBy": {
"type": "integer"
}
}
}
Returned Data
|
Field |
Description |
|
name |
Epic name |
|
description |
Epic description |
|
groupId |
Identifier of the group (scrum) to which the epic belongs |
|
color |
Epic color |
|
files |
Array of files attached to the epic |
|
createdBy |
Created by |
|
modifiedBy |
Modified by |
Error Handling
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred, please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred, please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the account administrator has allowed access to this application only for specific users |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Epics in Scrum: Overview of Methods
- Add Epic in Scrum tasks.api.scrum.epic.add
- Update Epic in Scrum tasks.api.scrum.epic.update
- Get Epic Fields by Its Identifier tasks.api.scrum.epic.get
- Get a list of epics tasks.api.scrum.epic.list
- Delete Epic tasks.api.scrum.epic.delete