Issue Types

post

https://app.financekey.com/OData/IssueTypes

The IssueType table, located in the Repo package, stores various types of issues that may occur within a project or organization. This table serves as a reference for easily identifying and categorizing any problems or challenges that arise during development or implementation processes. The table includes fields such as issue type ID, name, description, and necessary actions to resolve the issue. It also allows for the possibility of adding new issue types as necessary, providing flexibility for future developments or changes within the project. The IssueType table is a crucial component in effectively managing and addressing issues within a project.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

issueTypeId

string

required

length between 1 and 450

IssueType is a table that contains data related to different types of issues that may arise in a specific system or project. The table includes a primary key field called IssueTypeId, which is of data type nvarchar and has a maximum length of 450 characters. This field serves as a unique identifier for each individual issue type within the table. It is designed to ensure the accuracy and efficiency of data retrieval operations, as well as maintain data integrity within the table. With the IssueTypeId field, users can easily distinguish between different types of issues and associate them with corresponding data entries in the table.

description

string

required

length ≥ 1

Description is a field within the database table IssueType that is of the data type nvarchar. This field is used to provide a written explanation or summary of the specific issue type being recorded. It allows for a detailed description of the issue to be included in the database, providing a clear understanding of what the issue entails. The data type nvarchar allows for the description to be in a variable length format, ensuring that all necessary information can be captured accurately. With the use of this field, various issue types can be easily distinguished and thoroughly documented, leading to more effective data management and problem-solving.

comment

string | null

Miscellaneous notes and information for the entry or record.

badgeId

string

required

length between 1 and 32

The BadgeId field in the IssueType table is a nvarchar data type with a maximum length of 32 characters. This field stores a unique identifier for the type of issue being reported. It may contain any combination of letters, numbers, or special characters up to a maximum length of 32 characters. The BadgeId serves as a reference for differentiating between various types of issues and aids in organizing and categorizing them.

badgeImage

string | null

The BadgeImage field in the IssueType table is of data type nvarchar and can hold a maximum of 256 characters. It stores an image associated with a specific issue type, such as a warning symbol for a critical issue or a checkmark for a resolved issue. This field provides a visual representation of the issue type, making it more user-friendly and intuitive for users to identify and assign to relevant tasks or tickets. The use of nvarchar allows for flexibility in storing different types of image files, while the character limit ensures efficient storage and retrieval of data.

canSelect

boolean

The CanSelect field in the IssueType table denotes whether an issue type can be selected or not. It is a boolean data type, represented by a binary digit of either 1 or 0. A value of 1 indicates that the issue type can be selected, while a value of 0 means it cannot be selected. This field is useful for categorizing and filtering issues in a system, allowing for more efficient management and resolution.

canEdit

boolean

The CanEdit field in the IssueType table is a data type of bit, representing a binary value of either 1 or 0. This field is used to determine whether certain users or roles have the ability to edit the issue types within the table. If the value is set to 1, it indicates that the user or role has permissions to edit the issue types, while a value of 0 indicates that they do not have edit permissions. This field is important for managing and controlling access to the issue types in the table, ensuring that only authorized individuals are able to make changes.

Headers

content-type

string

enum

Defaults to application/json;odata.metadata=minimal;odata.streaming=true

Generated from available request content types

Response

200

Language

URL

Loading…

Response

Click Try It! to start a request and see the response here!