When submitting an item, users can define the Priority. By default, the Priority is set to Important.

Note: As the AsInt team performs the initial triage of the issue, we reserve the right to change the Priority based on the below definition.

Critical, Priority 1

1. The problem results in extremely serious interruption to a customer’s production system and has affected, or could affect, the entire user community.
2. Tasks that should be executed immediately cannot be executed because of a complete crash of the system, or by interruptions in the main functions of the production system.
3. Data integrity is compromised.
4. The service request required immediate processing, as the problem can result in financial losses.

Urgent, Priority 2

1. The problem results in extremely serious interruption to normal operations, or the issue will negatively impact the enterprise-wide production system rollout.
2. Import tasks cannot be performed In a production system, but the error impairs essential operations.
3. Processing can continue in a restricted manner.
4. Data Integrity may be at risk.
5. The service request requires timely processing, as the malfunction could cause serious interruptions to critical processes or negatively impact business decisions.

Important, Priority 3

1. The problem causes interruption to normal operations.
2. It does not prevent the operation of a system, or else there is a minor segregation in performance.
3. The error is attributed to malfunctioning or incorrect behavior of the Software.
4. The issue will impact a pilot or proof-of-concept deadline.

Recommendation, Priority 4

1. A recommended change to an existing feature to optimize a work process, or a recommended new feature to an existing application.
2. The change in the feature, or an additional new feature, does not prohibit existing normal use of the Software.
3. The service does not require timely processing, though escalation can occur to ensure the addition or change meets the customer’s needs.