extensions:teemip-request-mgmt
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| extensions:teemip-request-mgmt [2025/07/02 14:43] – cnaud | extensions:teemip-request-mgmt [2026/10/05 14:06] (current) – [Revision History] cnaud | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| level_hidden | level_hidden | ||
| collector_hidden | collector_hidden | ||
| - | version | + | version |
| - | release_dt | + | release_dt |
| - | TeemIp | + | TeemIp |
| - | iTop : 3.2.1+ | + | iTop : 3.3.0+ |
| code : teemip-ip-request-mgmt | code : teemip-ip-request-mgmt | ||
| localization | localization | ||
| Line 19: | Line 19: | ||
| keyword_tags | keyword_tags | ||
| dependencies_s | dependencies_s | ||
| - | download_wiki | + | download_wiki |
| github_wiki | github_wiki | ||
| - | php-max | + | php-max |
| ---- | ---- | ||
| Line 31: | Line 31: | ||
| ===== Revision History ===== | ===== Revision History ===== | ||
| ^ Version | ^ Version | ||
| - | | **3.2.0** | 2025-07-02 | + | | **3.3.0** |
| - | | 3.1.2 | 2024-08-14 | + | | 3.2.1 | 2026-05-04 |
| + | | 3.2.0 | ||
| + | | 3.1.2 | 2024-08-14 | ||
| | 3.1.1 | 2023-12-11 | | 3.1.1 | 2023-12-11 | ||
| | 3.1.0 | 2023-06-21 | | 3.1.0 | 2023-06-21 | ||
| Line 73: | Line 75: | ||
| ===== Installation ===== | ===== Installation ===== | ||
| - | Installation on a TeemIp | + | Installation on a teemIP |
| - | When adding the module on an iTop application, the process will depends on the iTop version: | + | When adding the module on an iTop application, |
| - | * For iTop 2.4.0 and higher, use the new [[https://www.itophub.io/wiki/page? | + | |
| - | * For iTop versions older than 2.3.x, use the [[https:// | + | |
| ===== Configuration ===== | ===== Configuration ===== | ||
| Line 262: | Line 262: | ||
| From the Helpdesk menu, click on the “New IP Request” link. User is then asked to select amongst the 6 types of requests: | From the Helpdesk menu, click on the “New IP Request” link. User is then asked to select amongst the 6 types of requests: | ||
| - | {{ classcreate_iprequest13x.png ?nolink}} | + | {{ classcreate_iprequest13x.png? |
| Once selection is done, the creation form is displayed (IPv4 subnet creation, in the example below). | Once selection is done, the creation form is displayed (IPv4 subnet creation, in the example below). | ||
| - | {{ classcreate_iprequest23x.png ?nolink}} | + | {{ classcreate_iprequest23x.png? |
| Line 275: | Line 275: | ||
| The **private log** is the preferred way for keeping track of the investigations or operations: copy/paste of command line results, summary of communications with a provider, etc. | The **private log** is the preferred way for keeping track of the investigations or operations: copy/paste of command line results, summary of communications with a provider, etc. | ||
| - | + | ||
| - | {{public-privatelog_iprequest3x.png}} | + | {{ public-privatelog_iprequest3x.png? |
| Each entry in the public or private log is tracked with the name of the user who updated it and when it was done. It cannot be modified nor deleted. | Each entry in the public or private log is tracked with the name of the user who updated it and when it was done. It cannot be modified nor deleted. | ||
| Line 286: | Line 286: | ||
| Once an IP request is created, it needs to be assigned to a team and agent before being further processed. For that to happen, select the Assign action in the list of menus available from the details page. | Once an IP request is created, it needs to be assigned to a team and agent before being further processed. For that to happen, select the Assign action in the list of menus available from the details page. | ||
| - | {{ details-popup-menu-iprequestotheractions3x.png }} | + | {{ details-popup-menu-iprequestotheractions3x.png? |
| Then select the Support team you want to assign the ticket to, as well as the agent from this team. | Then select the Support team you want to assign the ticket to, as well as the agent from this team. | ||
| - | {{ classassign_iprequest3x.png ?nolink}} | + | {{ classassign_iprequest3x.png? |
| < | < | ||
| Line 306: | Line 306: | ||
| </ | </ | ||
| - | {{ classprocess_iprequestipcreation13x.png ?nolink}} | + | {{ classprocess_iprequestipcreation13x.png? |
| - | {{ classprocess_iprequestipcreation23x.png ?nolink}} | + | {{ classprocess_iprequestipcreation23x.png? |
| < | < | ||
| Line 333: | Line 333: | ||
| </ | </ | ||
| - | {{ classprocess_iprequestsubnetcreation.png ?nolink}} | + | {{ classprocess_iprequestsubnetcreation.png? |
| Once the subnet is selected, pressing the " | Once the subnet is selected, pressing the " | ||
| Line 361: | Line 361: | ||
| For creation requests, the subnet or the subnet block, where the IP or subnet are supposed to be picked from, need to be eligible for automatic creation. This behaviour is driven buy a parameter named " | For creation requests, the subnet or the subnet block, where the IP or subnet are supposed to be picked from, need to be eligible for automatic creation. This behaviour is driven buy a parameter named " | ||
| - | {{ classdetails_ipv4subnet3x.png ?nolink}} | + | {{ classdetails_ipv4subnet3x.png? |
| - | {{ classdetails_ipv6block3x.png ?nolink}} | + | {{ classdetails_ipv6block3x.png? |
| ===== IP Request Life Cycle ===== | ===== IP Request Life Cycle ===== | ||
| All IP requests share the same life cycle. This one is pretty simple and can be summarized as follows: | All IP requests share the same life cycle. This one is pretty simple and can be summarized as follows: | ||
| - | {{ lifecycle_iprequest3x.png ?nolink}} | + | {{ lifecycle_iprequest3x.png? |
extensions/teemip-request-mgmt.1751467392.txt.gz · Last modified: by cnaud