This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
extensions:teemip-request-mgmt [2021/03/23 17:42] – [Revision History] cnaud | extensions:teemip-request-mgmt [2021/03/23 18:40] – [User profiles] cnaud | ||
---|---|---|---|
Line 35: | Line 35: | ||
===== Revision History ===== | ===== Revision History ===== | ||
^ Version | ^ Version | ||
- | | 2.7.1 | 2021-04-01 | + | | 2.7.1 | 2021-04-01 |
| 2.6.1 | 2020-05-08 | | 2.6.1 | 2020-05-08 | ||
| 2.6.0 | 2020-04-14 | | 2.6.0 | 2020-04-14 | ||
Line 49: | Line 49: | ||
===== Features ===== | ===== Features ===== | ||
- | This extension allows Hostmasters to manage tickets that are specific to the IP management world: creation, modification or deletion | + | This extension allows Hostmasters to manage tickets that are specific to the IP management world: creation, modification or release |
- | Management of IP tickets is done following a workflow that automates the standard tasks associated to IP tickets: selection of an IP within a subnet, selection of a subnet within a subnet block, for instance. Such workflow insures that tickets are managed according to a defined process. Only authorized users can manage an IP request and change its status. | + | Management of IP tickets is done following a workflow that automates the standard tasks associated to IP tickets: selection of an IP within a subnet, selection of a subnet within a subnet block, for instance. Such workflow insures that tickets are managed according to a defined process. Only authorized users can manage an IP request and change its status. Full automation is also available to the end users who have the correct profile and for subnet blocks or subnets that allow such comprehensive automation. |
At any time of the life of the ticket, the support agent can communicate with the customer via a “Public log.” He can also communicate with teams internal to his company through a “Private log”. | At any time of the life of the ticket, the support agent can communicate with the customer via a “Public log.” He can also communicate with teams internal to his company through a “Private log”. | ||
- | Starting for revision 2.5.1, the extension includes | + | TeemIp |
===== Licensing ===== | ===== Licensing ===== | ||
Line 156: | Line 156: | ||
| Target class | Instantiated class of object that the IP should be linked to | No | | | Target class | Instantiated class of object that the IP should be linked to | No | | ||
| Functional CI | CI of class " | | Functional CI | CI of class " | ||
- | | Link between IP and CI | IP attribute of the CI that the IP should be allocate to | No | | + | | CI's IP attribute |
== Specific information for IP address V6 creation == | == Specific information for IP address V6 creation == | ||
Line 175: | Line 175: | ||
| Target class | Instantiated class of object that the IP should be linked to | No | | | Target class | Instantiated class of object that the IP should be linked to | No | | ||
| Functional CI | CI of class " | | Functional CI | CI of class " | ||
- | | Link between IP and CI | IP attribute of the CI that the IP should be allocate to | No | | + | | CI's IP attribute |
== Specific information for IP update == | == Specific information for IP update == | ||
Line 255: | Line 255: | ||
===== User profiles ===== | ===== User profiles ===== | ||
- | By default, IP request management is restricted to the Hostmaster | + | By default, IP request management is restricted to the **IP Helpdesk agent** |