API

Quality management APIs

POST quality/issues/{qualityIssueId}/related-issues

Creates a new relation to other quality issue.

HTTP method POST
URI https://api.rambase.net/quality/issues/{qualityIssueId}/related-issues
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {qualityIssueId} Quality issue identifier
Integer, minimum 100000
Successful HTTP status code 201
API resource identifier 4624, version 1

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
<RelatedIssue>
2
     <RelationType
RelationType

Required/mandatory field

What type of relation it is

Applicable domain values can be found here

>
{Integer}</RelationType>
3
     <QualityIssue>
4
          <QualityIssueId
QualityIssueId

Required/mandatory field

Quality issue identifier

Minimum value: 100000

>
{Integer}</QualityIssueId>
5
     </QualityIssue>
6
</RelatedIssue>
1
{
2
     "relatedIssue": {
3
          "relationType
RelationType

Required/mandatory field

What type of relation it is

Applicable domain values can be found here

":
"{Integer}",
4
          "qualityIssue": {
5
               "qualityIssueId
QualityIssueId

Required/mandatory field

Quality issue identifier

Minimum value: 100000

":
"{Integer}"
6
          }
7
     }
8
}

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.
$showDomainDescriptions Boolean, optional Set to "true" to include domain descriptions for fields using domain values. See the Domain values page for more information. Default value is false.
$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
<RelatedIssue>
2
     <RelatedIssueId
RelatedIssueId

Relation identifier

>
{Integer}</RelatedIssueId>
3
     <RelationType
RelationType

What type of relation it is

Possible domain values can be found here

>
{Integer}</RelationType>
4
     <AddedAt
AddedAt

Date and time of creation

>
{Datetime}</AddedAt>
5
     <QualityIssue>
6
          <QualityIssueId
QualityIssueId

Quality issue identifier

>
{Integer}</QualityIssueId>
7
          <Status
Status

Status of quality issue. 1: Registering, 2: Analyzing, 4: Pending actions, 8: Reviewing, 9: Closed

Possible domain values can be found here

>
{Integer}</Status>
8
          <Description
Description

Description of quality issue

>
{String}</Description>
9
          <Title
Title

Title of the issue

>
{String}</Title>
10
          <DueDate
DueDate

Time and date when this issue should be resolved

>
{Datetime}</DueDate>
11
          <Responsible>
12
               <UserId
UserId

User identifier

>
{Integer}</UserId>
13
               <FirstName
FirstName

First name of the user

>
{String}</FirstName>
14
               <Name
Name

Name of the user

>
{String}</Name>
15
               <UserLink
UserLink

User reference

>
{String}</UserLink>
16
          </Responsible>
17
          <CreatedBy>
18
               <EmployeeId
EmployeeId

Employee identifier

>
{Integer}</EmployeeId>
19
               <LastName
LastName

Last name of employee

>
{String}</LastName>
20
               <FirstName
FirstName

First name of employee

>
{String}</FirstName>
21
               <EmployeeLink
EmployeeLink

Employee reference

>
{String}</EmployeeLink>
22
          </CreatedBy>
23
          <QualityIssueLink
QualityIssueLink

API reference to the object

>
{String}</QualityIssueLink>
24
     </QualityIssue>
25
</RelatedIssue>
1
{
2
     "relatedIssue": {
3
          "relatedIssueId
RelatedIssueId

Relation identifier

":
"{Integer}",
4
          "relationType
RelationType

What type of relation it is

Possible domain values can be found here

":
"{Integer}",
5
          "addedAt
AddedAt

Date and time of creation

":
"{Datetime}",
6
          "qualityIssue": {
7
               "qualityIssueId
QualityIssueId

Quality issue identifier

":
"{Integer}",
8
               "status
Status

Status of quality issue. 1: Registering, 2: Analyzing, 4: Pending actions, 8: Reviewing, 9: Closed

Possible domain values can be found here

":
"{Integer}",
9
               "description
Description

Description of quality issue

":
"{String}",
10
               "title
Title

Title of the issue

":
"{String}",
11
               "dueDate
DueDate

Time and date when this issue should be resolved

":
"{Datetime}",
12
               "responsible": {
13
                    "userId
UserId

User identifier

":
"{Integer}",
14
                    "firstName
FirstName

First name of the user

":
"{String}",
15
                    "name
Name

Name of the user

":
"{String}",
16
                    "userLink
UserLink

User reference

":
"{String}"
17
               },
18
               "createdBy": {
19
                    "employeeId
EmployeeId

Employee identifier

":
"{Integer}",
20
                    "lastName
LastName

Last name of employee

":
"{String}",
21
                    "firstName
FirstName

First name of employee

":
"{String}",
22
                    "employeeLink
EmployeeLink

Employee reference

":
"{String}"
23
               },
24
               "qualityIssueLink
QualityIssueLink

API reference to the object

":
"{String}"
25
          }
26
     }
27
}

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 101015 HTTP 404 Permission not found
Error 101420 HTTP 404 Setting definition not found
Error 105978 HTTP 400 Relation to the other object should be added using different API.
Error 105979 HTTP 400 Cannot add relation to itself.
Error 100018 HTTP 404 Document {0} not found