Ticket System – creating a task
The integrated ticket system plays a huge part within ConnectOS. Due to its existence tasks and project can be organized way more efficiently. Therefore a lot of time can be saved working on it.
subtitles will be available soon
Ticket System – creating a task
The integrated ticket system plays a huge part within ConnectOS. Due to its existence tasks and project can be organized way more efficiently. Therefore a lot of time can be saved working on it.
subtitles will be available soon
Ticket System – creating a task
The integrated ticket system plays a huge part within ConnectOS. Due to its existence tasks and project can be organized way more efficiently. Therefore a lot of time can be saved working on it.
subtitles will be available soon
ConnectOS was developed to support corporations in the modern working world and of course to drive the digital transformation forward. ConnectOS is structured into different modules, like time management, ERP or Finances. These modules can be individually activated depending on the employee or department. Therefore users only have insight into the areas they actually need for their work.
The integrated ticket system plays a huge part in this context, since tasks and project can be organized way more efficiently. Therefore a lot of time can be saved working on it. Following, in this post we will focus on ConnectOS’ ticket system and its usage.
1.1
1.1 creating a ticket via the tasks module
There are many ways to create a ticket but of course the most obvious one is to do so directly via the tasks module. The tasks module can basically be seen as the management tool of ConnectOS’ ticket system.
In order to create a new ticket has to be clicked to open the option menu. The task can for example be assigned to a company or a project. Additionally things like the subject, the level of importance and wich team should work on it can be defined. Additionally, it is also possible to define a responsible person. If no one was declared the responsible person, the ticket will be put in a “ticket pool” of the chosen team. Something that can also be defined is the amount of time that should be used to complete a task as well as a reward when the ticket gets finished.
1.2
1.2 adding information to a ticket
In order to complete a task to full satisfaction, a detailed description is of great advantage. But a description doesn’t always have to be simply text, it can also be audio or video based. Of course it is also possible to add additional material like files, pictures or videos, wether be it to create a more clear description or because it is needed to complete the task. These additional files can simply be added by clicking .
In addition, a task can also be saved as a template so it can be reused multiple times.
2.1
2.1 creating a form as a base for ticket creation
Of course this isn’t the only way to create a ticket. An other option is to create a (ticket) form. This can be done in ConnectOS’ report designer, which can be found in the submenu of the menu point called options. Simply click + to open the option menu to create the new form where things like the name as well as the type of form can be defined. – However, something to consider is that there are different form options for different form results. Therefore when creating a ticket form the option general form needs to be chosen. Of course things like tags can be defined and additional files can be added as well.
2.2
2.2 completing the ticket form
In order to actually create the form template, EDIT needs to be clicked so an option menu similar to a page builder is opened. When clicking on + a new section is created. For this section different content sections can be defined simply by clicking . There are many different options to choose from, like for example between a text field, priority options or a field for adding additional data.
3.1
3.1 creating a ticket via the workflow module
The third and most versatile way to create a ticket is to do so via the workflow module. The workflow module can almost be seen as the heart of ConnectOS, since it plays a roll in almost every other module. Additionally the workflow module profits immensely from ConnectOS’ integrated AI and machine learning.
But in order to manage tickets via the workflow module workflow > hub in the menu bar left has to be clicked. All information coming from exterior sources are collected and passed down from there. Withe the help of POP3 and IMAP e-mails can be retrieved from a mal server. But thats not all. – Even Information from Twitter, Facebook or Microsoft Office 365 can be retrieved with the integrated API. Of course the classic approach to retrieve data from basic messenger platforms like SMS, WhatsApp or Telegram is included as well.
3.2
3.2 creating a ticket via the workflow module
All messages no matter their source, have to be controlled by a set of rules, which can be defined individually. – It is comparable to a flexible file structure therefore all the data can be individually processed depending on the type of its source. For instance through tags or company affiliation.
First the type of message and who it is from is checked. Depending on the definition of rule set, the message is automatically transformed int a task, or it has to run through additional steps before being transformed into a task. Of course the ticket settings are the same as in section 1.1 and 1.2.
3.3
3.3 recurring Tickets
Are there for instance any recurring tasks in a team? Of course that’s no problem either because even that can be automized. This can be defined in projects & boxes > workflow. Following, you only have to choose the according project under the category WORKFLOW. Under the option task template the task that should be repeated can be defined. In addition, it is also possible to set how often it should be repeated and its intervals. In other words, these options have tobe set once and the rest happens on its own.
In conclusion there are many easy ways to create a ticket. And as soon as the ticket was created it can be dealt with by the chosen team, which is getting informed about the new task via PM. Of course all information about the process on working on a ticket (for admin and employee) can be found in the post HOW TO: tasks introduction.
ConnectOS was developed to support corporations in the modern working world and of course to drive the digital transformation forward. ConnectOS is structured into different modules, like time management, ERP or Finances. These modules can be individually activated depending on the employee or department. Therefore users only have insight into the areas they actually need for their work.
The integrated ticket system plays a huge part in this context, since tasks and project can be organized way more efficiently. Therefore a lot of time can be saved working on it. Following, in this post we will focus on ConnectOS’ ticket system and its usage.
1.1
1.1 creating a ticket via the tasks module
There are many ways to create a ticket but of course the most obvious one is to do so directly via the tasks module. The tasks module can basically be seen as the management tool of ConnectOS’ ticket system.
In order to create a new ticket has to be clicked to open the option menu. The task can for example be assigned to a company or a project. Additionally things like the subject, the level of importance and wich team should work on it can be defined. Additionally, it is also possible to define a responsible person. If no one was declared the responsible person, the ticket will be put in a “ticket pool” of the chosen team. Something that can also be defined is the amount of time that should be used to complete a task as well as a reward when the ticket gets finished.
1.2
1.2 adding information to a ticket
In order to complete a task to full satisfaction, a detailed description is of great advantage. But a description doesn’t always have to be simply text, it can also be audio or video based. Of course it is also possible to add additional material like files, pictures or videos, wether be it to create a more clear description or because it is needed to complete the task. These additional files can simply be added by clicking .
In addition, a task can also be saved as a template so it can be reused multiple times.
2.1
2.1 creating a form as a base for ticket creation
Of course this isn’t the only way to create a ticket. An other option is to create a (ticket) form. This can be done in ConnectOS’ report designer, which can be found in the submenu of the menu point called options. Simply click + to open the option menu to create the new form where things like the name as well as the type of form can be defined. – However, something to consider is that there are different form options for different form results. Therefore when creating a ticket form the option general form needs to be chosen. Of course things like tags can be defined and additional files can be added as well.
2.2
2.2 completing the ticket form
To actually create the form template, EDIT needs to be clicked so an option menu similar to a page boulder is opened. When clicking on + a new section is created. For this section different content sections can be defined simply by clicking . There are many different options to choose from, like for example between a text field, priority options or a field for adding additional data.
3.1
3.1 creating a ticket via the workflow module
The third and most versatile way to create a ticket is to do so via the workflow module. The workflow module can almost be seen as the heart of ConnectOS, since it plays a roll in almost every other module. Additionally the workflow module profits immensely from ConnectOS’ integrated AI and machine learning.
But in order to manage tickets via the workflow module workflow > hub in the menu bar left has to be clicked. All information coming from exterior sources are collected and passed down from there. Withe the help of POP3 and IMAP e-mails can be retrieved from a mal server. But thats not all. – Even Information from Twitter, Facebook or Microsoft Office 365 can be retrieved with the integrated API. Of course the classic approach to retrieve data from basic messenger platforms like SMS, WhatsApp or Telegram is included as well.
3.2
3.2 creating a ticket via the workflow module
All messages no matter their source, have to be controlled by a set of rules, which can be defined individually. – It is comparable to a flexible file structure therefore all the data can be individually processed depending on the type of its source For instance through tags or company affiliation.
First the type of message and who it is from is checked. Depending on the definition of rule set, the message is automatically transformed int a task, or it has to run through additional steps before being transformed into a task. Of course the ticket setting are the same as in section 1.1 and 1.2.
3.3
3.3 recurring Tickets
Are there for instance any recurring tasks in a team? Of course that’s no problem either because even that can be automized. This can be defined in projects & boxes > workflow. Following, you only have to choose the according project under the category WORKFLOW. Under the option task template the task that should be repeated can be defined. In addition, it is also possible to set how often it should be repeated and its intervals. In other words, these options have tobe set once and the rest happens on its own.
In conclusion there are many easy ways to create a ticket. And as soon as the ticket was created it can be dealt with by the chosen team, which is getting informed about the new task via PM. Of course all information about the process on working on a ticket (for admin and employee) can be found in the post HOW TO: tasks introduction.
ConnectOS was developed to support corporations in the modern working world and of course to drive the digital transformation forward. ConnectOS is structured into different modules, like time management, ERP or Finances. These modules can be individually activated depending on the employee or department. Therefore users only have insight into the areas they actually need for their work.
The integrated ticket system plays a huge part in this context, since tasks and project can be organized way more efficiently. Therefore a lot of time can be saved working on it. Following, in this post we will focus on ConnectOS’ ticket system and its usage.
1. creating a ticket via the tasks module
There are many ways to create a ticket however, of course the most obvious one is to do so directly via the tasks module. The tasks module can basically be seen as the management tool of ConnectOS’ ticket system.
In order to create a new ticket has to be clicked to open the option menu. The task can for example be assigned to a company or a project. Additionally things like the subject, the level of importance and wich team should work on it can be defined. Additionally, it is also possible to define a responsible person. If no one was declared the responsible person, the ticket will be put in a “ticket pool” of the chosen team. Something that can also be defined is the amount of time that should be used to complete a task as well as a reward when the ticket gets finished.
1.1
1.2
1.2 adding information to a ticket
In order to complete a task to full satisfaction, a detailed description is of great advantage. But a description doesn’t always have to be simply text, it can also be audio or video based. Of course it is also possible to add additional material like files, pictures or videos, wether be it to create a more clear description or because it is needed to complete the task. These additional files can simply be added by clicking .
In addition, a task can also be saved as a template so it can be reused multiple times.
2.1 creating a form as a base for ticket creation
Of course this isn’t the only way to create a ticket. An other option is to create a (ticket) form. This can be done in ConnectOS’ report designer, which can be found in the submenu of the menu point called options. Simply click + to open the option menu to create the new form where things like the name as well as the type of form can be defined. – However, something to consider is that there are different form options for different form results. Therefore when creating a ticket form the option general form needs to be chosen. Of course things like tags can be defined and additional files can be added as well.
2.1
2.2
2.2 completing the ticket form
To actually create the form template, EDIT needs to be clicked so an option menu similar to a page boulder is opened. When clicking on + a new section is created. For this section different content sections can be defined simply by clicking . There are many different options to choose from, like for example between a text field, priority options or a field for adding additional data.
3.1 creating a ticket via the workflow module
The third and most versatile way to create a ticket is to do so via the workflow module. The workflow module can almost be seen as the heart of ConnectOS, since it plays a roll in almost every other module. Additionally the workflow module profits immensely from ConnectOS’ integrated AI and machine learning.
But in order to manage tickets via the workflow module workflow > hub in the menu bar left has to be clicked. All information coming from exterior sources are collected and passed down from there. Withe the help of POP3 and IMAP e-mails can be retrieved from a mal server. But thats not all. – Even Information from Twitter, Facebook or Microsoft Office 365 can be retrieved with the integrated API. Of course the classic approach to retrieve data from basic messenger platforms like SMS, WhatsApp or Telegram is included as well.
3.1
3.2
3.2 creating a ticket via the workflow module
All messages no matter their source, have to be controlled by a set of rules, which can be defined individually. – It is comparable to a flexible file structure therefore all the data can be individually processed depending on the type of its source. For instance through tags or company affiliation.
First the type of message and who it is from is checked. Depending on the definition of rule set, the message is automatically transformed int a task, or it has to run through additional steps before being transformed into a task. Of course the ticket setting are the same as in section 1.1 and 1.2.
3.3 recurring tickets
Are there for instance any recurring tasks in a team? Of course that’s no problem either because even that can be automized. This can be defined in projects & boxes > workflow. Following, you only have to choose the according project under the category WORKFLOW. Under the option task template the task that should be repeated can be defined. In addition, it is also possible to set how often it should be repeated and its intervals. In other words, these options have tobe set once and the rest happens on its own.
3.3
In conclusion there are many easy ways to create a ticket. And as soon as the ticket was created it can be dealt with by the chosen team, which is getting informed about the new task via PM. Of course all information about the process on working on a ticket (for admin and employee) can be found in the post HOW TO: tasks introduction.