Configuration
In a company, it often happens that people from different departments have to work together to deliver a Service Request. Octopus enables End Users to receive Tasks and participate in the execution of a request. They are called "External Assignees". The delivery of the Service Request is more...
Files attached to Octopus data ("Attached files" tab in Incidents/SR, Problems, CI, Users, etc.) are all saved on your network, and not on the Octopus.
To start, it is important to understand that there are no perfect categories. The main objective of an adequate categorization system is to represent a clear comprehension of user reported problematic. This approach favours a better comprehension of the IT infrastructure use when the time comes to...
From the 4.2.230 version it is possible to activate two new modes on the Web Portal. The modern mode includes the tiles and the colours. Activating the modern mode requires some modification and preparation, but above all, it implicates all the teams that are visible on the Web...
The subject of a request is an important element, as it is often the basic information that is visible in a list.
By default, Octopus subjects take the name of the request, but there are two options that help to automatically get more specific subjects:
The alternate subject
Uses...
Octopus can connect to your centralized authentication system (Single Sign-On) to facilitate the access to the application. (Note that this authentication is only available to the hosted customers)
Unique authentication can be used independently for the following components:
The "task" concept is applied in Octopus for service requests, changes and problems. Tasks are created to reflect the execution process ("workflow") of a service request, the steps for preparing and implementing a change and the tasks involved in analyzing a problem; in all cases, they can be...
Pages
