Issues
Main menu for all issues. Can be added to the main menu. Possible to add listviews.
Deem Insight is very flexible regarding the setup for both activities and issues. But the idea behind having both types of tasks is to diversify the use, where activities are for simpler tasks (e.g. follow up customers), and issues can be more complex. Usually type, workflow and statuses are completely different for these two types of tasks.
There is also a possibility to create a sub issue, which will be linked to the main issue. The sub issue is an ordinary issue, and is handled as an ordinary issue, but there is an existing link between the two issues.
The following parameters are mandatory for the issues:
| Field | Description |
|---|---|
| Project | The project must already exist, and available projects will be found in the dropdown list. The project is always attached to an account. Once a project has been added to an issue, it can not be removed or edited. |
| Type | Types are custom, and can be set up in record types (there are some standards which can be used). You can also set default status for issue types. |
| Account | The account is automatically set based on the project selected. |
| Assignee | You can choose assignee in the dropdown list. All contacts that are either agents or has main account as the account linked to the project, are in the drop down list. If left blank the creator will be set as the assignee. |
| Name | There is no need for a unique name for each issue. |
| Key | The key is automatically generated based on the selected account. |
| Reporter | You can choose reporter in the dropdown list. All contacts that are either agents or has main account as the account linked to the project, are in the drop down list. |
| Priority | Priorities are custom, and can be set up in priorities (there are some standards which can be used). Default priority can be ticked off in priorities. If no default priority is set, the order in the priority column will be used. |
| Created time | Automatically generated when the issue is created. |
| Status | Statuses are custom, and can be set up in statuses (there are some standards which can be used). The available statuses varies depending on where you are in the workflow. The link between statuses and workflow are set in workflow in the admin menu. |
The following parameters are optional for the issues:
| Field | Description |
|---|---|
| Notes | Free text field. |
| Due date | Due date can be set in the drop-down calendar. If a date is not selected, either left open or the current date will be filled out e.g. if the issue is set to be automatically closed. |
| Milestone | Milestones are custom, and can be set up in milestones. |
| Process | Processes are custom, and can be set up in processes. |
| Reference | Free text field. |
| Resolution | Resolution types are custom, and can be set up in resolutions (there are some standards which can be used). |
| Resolution description | Free text field. |