Issues
Modifies the provided properties of the specified issue to match the values provided in the request.
Setting a property value to null in the request will set the corresponding property value to null on the issue. However, omitting a property from the request body entirely will leave that property's current value on the issue unchanged. Also, setting an object (other than "properties") to null will have the same effect as setting each individual property in that object to null.
Permissions
To use this endpoint, the user is required to have different ProjectWise Forms permissions (for the project, or for the issue's associated form definition if form definition security is specified) based on the changes being made:
- Change to the
statusproperty: Approve (Forms_ApproveAccess) permission - Change to the
assigneeorassigneesproperty: Assign (Forms_AssignAccess) or Approve permission - Changes to other properties: Create/Modify (
Forms_CreateAccess) permission
Full Access (Forms_FullAccess) will satisfy all of these requirements.
Authentication
Requires Authorization header with valid Bearer token for scope issues:modify.
For more documentation on authorization and how to get access token visit OAUTH2 Authorization page.
Request parameters
The ID of the issue to modify.
Request headers
OAuth access token with scope issues:modify
Setting to application/vnd.bentley.itwin-platform.v1+json is recommended.
Request body
Brief title/description of the issue.
Detailed description of the issue.
The date by which an action should be taken on this issue. Applications will use this to determine whether an issue is near due or overdue.
The issue's new workflow status, if applicable.
Text of a comment to associated with the status change. This property MUST NOT be set UNLESS the 'status' property is also set AND the workflow for the issue's type allows a workflow note to be added for transitions from the old status to the new status.
For cases when an issue is assigned to multiple people and/or roles, this lists all of them rather than just the primary assignee.
Origin info. An object linking the issue to an entity outside the Issues service, such as a file in Storage or an element in an iModel, that the issue was created to pertain to.
Origin info. Describes a rectangular-prism area of the model that the issue pertains to.
Origin info. Describes a point in 3D space that the issue pertains to. May or may not be based on the position of a particular element.
Origin info. Describes a view of the model that shows the relevant elements that the issue pertains to.
The date and time represented in the model where the issue occurred (if in a 4D model).
Any custom properties that are defined in the Form Designer for issues of this issue's type may be set here. If this object is omitted or set to null, all custom properties will retain their current values.
Example
Brief title/description of the issue.
Detailed description of the issue.
The date by which an action should be taken on this issue. Applications will use this to determine whether an issue is near due or overdue.
The issue's new workflow status, if applicable.
Text of a comment to associated with the status change. This property MUST NOT be set UNLESS the 'status' property is also set AND the workflow for the issue's type allows a workflow note to be added for transitions from the old status to the new status.
For cases when an issue is assigned to multiple people and/or roles, this lists all of them rather than just the primary assignee.
Origin info. An object linking the issue to an entity outside the Issues service, such as a file in Storage or an element in an iModel, that the issue was created to pertain to.
Origin info. Describes a rectangular-prism area of the model that the issue pertains to.
Origin info. Describes a point in 3D space that the issue pertains to. May or may not be based on the position of a particular element.
Origin info. Describes a view of the model that shows the relevant elements that the issue pertains to.
The date and time represented in the model where the issue occurred (if in a 4D model).
Any custom properties that are defined in the Form Designer for issues of this issue's type may be set here. If this object is omitted or set to null, all custom properties will retain their current values.
Example
Brief title/description of the issue.
Detailed description of the issue.
The date by which an action should be taken on this issue. Applications will use this to determine whether an issue is near due or overdue.
The issue's new workflow status, if applicable.
Text of a comment to associated with the status change. This property MUST NOT be set UNLESS the 'status' property is also set AND the workflow for the issue's type allows a workflow note to be added for transitions from the old status to the new status.
For cases when an issue is assigned to multiple people and/or roles, this lists all of them rather than just the primary assignee.
Origin info. An object linking the issue to an entity outside the Issues service, such as a file in Storage or an element in an iModel, that the issue was created to pertain to.
Origin info. Describes a rectangular-prism area of the model that the issue pertains to.
Origin info. Describes a point in 3D space that the issue pertains to. May or may not be based on the position of a particular element.
Origin info. Describes a view of the model that shows the relevant elements that the issue pertains to.
The date and time represented in the model where the issue occurred (if in a 4D model).
Any custom properties that are defined in the Form Designer for issues of this issue's type may be set here. If this object is omitted or set to null, all custom properties will retain their current values.
Example
Response 200 OK
Indicates that the changes were successfully made. The response body contains the issue's data after modification, including both changed and unchanged properties. Note: If a workflow transition occurred, some properties may have been automatically changed in addition to the properties the client specified to change in the request.
Response 401 Unauthorized
This response indicates that request lacks valid authentication credentials. Access token might not been provided, issued by the wrong issuer, does not have required scopes or request headers were malformed.
Response 409 Conflict
This response indicates that the issue the user attempted to update does not exist (or is inaccessible due to insufficient permissions).
Response 422 Unprocessable Entity
This response indicates that there is a problem with the format of the request body. Most likely causes: An unrecognized standard or custom property was added, a standard property was set in the 'properties' object instead of the top-level object, the body is invalid JSON, or a property was set to a value of the wrong type.
Response 429 Too many requests
This response indicates that the user has sent too many requests in a given amount of time.
The number of requests exceeds the rate-limit for the client subscription.
Issue (get)
Contains the full data of this issue. Any property that was never set on the issue will be omitted from the response.
Unique identifier for this instance. Read-only.
Name that should be used to show this issue in a list of issues in the UI. This is read-only. Project managers can configure how this is generated; usually, it will be the value of another property.
The ID of the form definition that this issue was created with. Note: This property will only be returned during the 'Get issue details' query, not in the result of a Create or Modify operation.
Brief title/description of the issue.
Detailed description of the issue.
Read-only. Describes which domain of work the issue involves, which determines what applications will show it. Automatically set based on the form definition that was used to create the issue.
An human-readable identifier for the issue, consisting of an alphanumeric prefix (that can be configured by the project administrator) followed by an auto-incrementing number. Read-only.
The date by which an action should be taken on this issue. Applications will use this to determine whether an issue is near due or overdue.
The current workflow status the issue is in right now.
Indicates whether the issue's status is an Open, Closed, or Draft status. This property is read-only.
A RBG hexadecimal color string, e.g. #ff0000. Read-only. If set, this gives a hint for how to highlight the issue in a list of issues based on its current workflow status.
For cases when an issue is assigned to multiple people and/or roles, this lists all of them rather than just the primary assignee.
The display name of the user who originally created this issue. Read-only.
The date and time when this issue was originally created. Read-only.
The display name of the user who most recently made a change to this issue. Read-only.
The date and time when this issue was most recently edited. Read-only.
Origin info. An object linking the issue to an entity outside the Issues service, such as a file in Storage or an element in an iModel, that the issue was created to pertain to.
Origin info. Describes a rectangular-prism area of the model that the issue pertains to.
Origin info. Describes a point in 3D space that the issue pertains to. May or may not be based on the position of a particular element.
Origin info. Describes a view of the model that shows the relevant elements that the issue pertains to.
The date and time represented in the model where the issue occurred (if in a 4D model).
Contains all issue-type-specific and user-defined properties that were set on this issue. Properties set here may be strings, numbers, booleans, arrays, or objects, depending on how the project's administrator defined them in the Form Designer.
Links to related entities, if applicable.
Issue (update)
Provides new property values for properties that are being changed in the update. All properties are optional. Omitting a property will keep its current value intact.
Brief title/description of the issue.
Detailed description of the issue.
The date by which an action should be taken on this issue. Applications will use this to determine whether an issue is near due or overdue.
The issue's new workflow status, if applicable.
Text of a comment to associated with the status change. This property MUST NOT be set UNLESS the 'status' property is also set AND the workflow for the issue's type allows a workflow note to be added for transitions from the old status to the new status.
For cases when an issue is assigned to multiple people and/or roles, this lists all of them rather than just the primary assignee.
Origin info. An object linking the issue to an entity outside the Issues service, such as a file in Storage or an element in an iModel, that the issue was created to pertain to.
Origin info. Describes a rectangular-prism area of the model that the issue pertains to.
Origin info. Describes a point in 3D space that the issue pertains to. May or may not be based on the position of a particular element.
Origin info. Describes a view of the model that shows the relevant elements that the issue pertains to.
The date and time represented in the model where the issue occurred (if in a 4D model).
Any custom properties that are defined in the Form Designer for issues of this issue's type may be set here. If this object is omitted or set to null, all custom properties will retain their current values.
Primary Assignee
An object describing the primary user or role assigned to an issue.
The GUID identifying the user or role.
The role's name, or the user's given name and surname, as it should be displayed in an application.
Secondary Assignee
An object describing one of potentially several users or roles assigned to an issue.
The GUID identifying the user or role.
The role's name, or the user's given name and surname, as it should be displayed in an application.
If true, this is a role; otherwise, it is an individual user.
bounding-box
Origin info. Describes a rectangular-prism-shaped region in a 3D model that the issue pertains to.
Model Pin
Origin info. Associates an issue with a single point in a model that does not necessarily correspond to a model element.
String describing the relevance of the pin's location.
Model View
Origin info. Describes the view that was visible when the issue was created.
The ID of a saved view showing the issue.
point3D
camera
Endpoint of a vector from the origin that determines which direction appears as upwards in the view.
Determines the zoom level of the camera, i.e. how much to multiply 1 distance unit in the view by to get the actual distance in meters in the model. Either this or fieldOfView should be specified, but not both.
Determines the number of degrees in the circular arc around the camera's position that is visible in the view. Either this or viewToWorldScale should be specified, but not both.
location
Origin info. The geographical location the issue pertains to.
The degrees latitude of the issue's location. North: positive, south: negative.
The degrees longitude of the issues location. East: positive, west: negative.
The geographical elevation above/below sea level. Units for this property are not standardized, so an application should not make assumptions about this property's value set by other applications unless that other application's units are known.
A string describing the significance of this location.
source-entity-file
Represents a file in Storage about which an issue was created.
ID used to identify the file in the Storage API.
ID of the folder containing the file in the Storage API.
Name of the file, including extension.
source-entity-i-model-element
Represents an element in an iModel about which an issue was created.
ID of the iModel containing the element, as it exists in the iModels API.
ID of the element. Can be a hexadecimal numeric string (space-separated to include multiple elements) or a presentation key.
ID of the changeset where the issue was created.
Name of the model.
source-entity-links-file
Links to retrieve the related file, and the folder that contains it, from the Storage API.
source-entity-links-i-model-element
Links to retrieve the related element's specific changeset, or iModel in general, from the iModels API.
Dynamic Object
An object whose properties can vary depending on user customization within the project.
link
error-response
Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.
Short string indicating the general category of error that occurred, such as '{Resource}NotFound'.
Longer string explaining to developers why the error occurred.
If relevant, this is the name of the property, URL template parameter, or query parameter that caused the error.
Error
Contains error information and an optional array of more specific errors.
One of a server-defined set of error codes.
A human-readable representation of the error.
The target of the error.
Error Details
Contains error information.
One of a server-defined set of error codes.
A human-readable representation of the error.
The target of the error.
Error Response
Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.