...
Description of default fields
Field name | Description | ||||||
---|---|---|---|---|---|---|---|
Project | Select the product to which you want the Issue to apply:
| ||||||
Issue type | Select the type that is closest to the purpose of the Issue:
| ||||||
Status | By default this should be set to Open when creating a new Issue | ||||||
Components | Not used | ||||||
Priority | Indicate the priority of the Issue. Blocker Work with appl. or production cannot run.
| ||||||
IX Prio | Integration X’s internal priority. | ||||||
Summary | Write a summary of the Issue. Please make it short, descriptive and distinguishable from other issues.
| ||||||
Description | Enter a detailed description of the issue here. Please be as precise as possible and consider adding references to examples that can be tracked by the Integration X support teams.
| ||||||
| Creates the current issue. |
Note |
---|
Some fields may not be available or have different appearance or different selectable options according to individual agreement. |
...
Most of these fields cannot be edited. They are merely available for information and filtering purposes.
Field name | Description |
---|---|
Assignee | The Integration X agent(s) assigned to the Issue. |
Group share | The group that can view and edit the Issue. |
Labels | Integration X may from time to time add new labels in order to tag individual Issues to create virtual groups. |
Time tracking | A summary of the time spend on an Issue - typically used for Issue that are billable. |
Due date | The date for which a solution is expected to be available. |
Adding comments
When an issue is being worked on, it is possible to add comments. Comments are similar to the Description field in terms of options for formatting, adding attachments etc. When a comment is entered, it can be modified only by the user who entered it.
...
Below find an explanation of the most important statuses.
Status | Next action expected by | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Open |
| The Issue is open for modifications. | ||||||||||||
In progress |
| The Issue is being worked on. | ||||||||||||
Resolved |
| The Issue is resolved, but not closed. It will be closed by Integration X. | ||||||||||||
Reopened |
| The Issue was resolved, but reopened by Integration X. | ||||||||||||
Awaiting approval |
| The issue is awaiting approval by the customer. | ||||||||||||
Closed | - | The Issue is closed. Not further changes can be made. | ||||||||||||
Approved |
| The solution to the Issue is approved by customer. | ||||||||||||
Pending |
| The Issue is pending - likely waiting for more information or internal review. | ||||||||||||
Rejected |
| The Issue is rejected by Integration X. A work-around is typically indicated. | ||||||||||||
Awaiting customer input |
| The Issue is waiting for the customer to provide input. | ||||||||||||
Customer input provided |
| The customer has provided input. Now waiting on Integration X to continue. |
Changing statuses
As an Issue appears in a certain status, there will be actions to progress. These actions vary depending on the actual status.
...