This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
extensions:teemip-request-mgmt [2023/06/20 15:46] – [IP Request Management] cnaud | extensions:teemip-request-mgmt [2025/07/02 16:49] (current) – [IP Request Life Cycle] cnaud | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{ iprequest.png}} | + | {{ picto_iprequestmanagement.png}} |
| | ||
---- dataentry summary ---- | ---- dataentry summary ---- | ||
Line 6: | Line 6: | ||
index_hidden | index_hidden | ||
level_hidden | level_hidden | ||
- | version | + | collector_hidden |
- | release_dt | + | version |
- | TeemIp | + | release_dt |
- | iTop : 3.x | + | TeemIp |
+ | iTop : 3.2.1+ | ||
code : teemip-ip-request-mgmt | code : teemip-ip-request-mgmt | ||
localization | localization | ||
Line 18: | Line 19: | ||
keyword_tags | keyword_tags | ||
dependencies_s | dependencies_s | ||
- | download_wiki | + | download_wiki |
github_wiki | github_wiki | ||
- | php-max | + | php-max |
---- | ---- | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
TeemIp' | TeemIp' | ||
Line 39: | Line 30: | ||
===== Revision History ===== | ===== Revision History ===== | ||
- | ^ Version | + | ^ Version |
- | | 3.1.0 | 2023-06-21 | + | | **3.2.0** |
- | | 3.0.1 | 2022-09-09 | + | | 3.1.2 | 2024-08-14 |
- | | 3.0.0 | 2022-01-10 | + | | 3.1.1 | 2023-12-11 |
- | | 2.7.1 | 2021-04-01 | + | | 3.1.0 | 2023-06-21 |
- | | 2.6.1 | 2020-05-08 | + | | 3.0.1 | 2022-09-09 |
- | | 2.6.0 | 2020-04-14 | + | | 3.0.0 | 2022-01-10 |
- | | 2.5.1 | 2019-12-10 | + | | 2.7.1 | 2021-04-01 |
- | | 2.5.0 | 2019-09-24 | + | | 2.6.1 | 2020-05-08 |
- | | 2.4.0 | 2019-02-09 | + | | 2.6.0 | 2020-04-14 |
- | | 2.3.0 | 2018-08-28 | + | | 2.5.1 | 2019-12-10 |
- | | 2.2.0 | | + | | 2.5.0 | 2019-09-24 |
- | | 2.1.2 | 2017-11-11 | + | | 2.4.0 | 2019-02-09 |
- | | 2.1.1 | 2016-12-19 | + | | 2.3.0 | 2018-08-28 |
+ | | 2.1.2 | 2017-11-11 | ||
+ | | 2.1.1 | 2016-12-19 | ||
Line 63: | Line 56: | ||
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”. | ||
- | TeemIp IP Request Management includes a dedicated portal that is described [[2_x: | + | TeemIp IP Request Management includes a dedicated portal that is described [[2_x: |
===== Licensing ===== | ===== Licensing ===== | ||
Line 98: | Line 91: | ||
Once installed, the module will add a menu group called IP Helpdesk where IP requests will be managed from. | Once installed, the module will add a menu group called IP Helpdesk where IP requests will be managed from. | ||
- | {{ details_menu_iphelpdesk3x.png }} | + | {{ details_menu_iphelpdesk3x.png? |
The overview dashboard allows agents and managers to monitor the helpdesk activity. It displays a set of 6 dashlets: | The overview dashboard allows agents and managers to monitor the helpdesk activity. It displays a set of 6 dashlets: | ||
Line 108: | Line 101: | ||
* The number of Open IP requests, grouped by organization. | * The number of Open IP requests, grouped by organization. | ||
- | {{ dashboard_iprequests.PNG }} | + | {{ dashboard_iprequests.PNG? |
===== IP Request ===== | ===== IP Request ===== | ||
- | {{iprequest.png | + | {{iprequest.png? |
IP requests in TeemIp are focusing on IP management. A catalogue of 6 types of IP requests have been defined, each of them focusing on a specific request: | IP requests in TeemIp are focusing on IP management. A catalogue of 6 types of IP requests have been defined, each of them focusing on a specific request: | ||
Line 149: | Line 142: | ||
== Specific information for IP address V4 creation == | == Specific information for IP address V4 creation == | ||
- | {{icons8-rj45-48.png | + | {{icons8-rj45-48.png? |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 168: | Line 161: | ||
== Specific information for IP address V6 creation == | == Specific information for IP address V6 creation == | ||
- | {{icons8-rj45v6-48.png | + | {{icons8-rj45v6-48.png? |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 187: | Line 180: | ||
== Specific information for IP update == | == Specific information for IP update == | ||
- | {{icons8-rj45-48.png | + | {{icons8-rj45-48.png? |
- | {{icons8-rj45v6-48.png | + | {{icons8-rj45v6-48.png? |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 200: | Line 193: | ||
== Specific information for IP release == | == Specific information for IP release == | ||
- | {{icons8-rj45-48.png | + | {{icons8-rj45-48.png? |
- | {{icons8-rj45v6-48.png | + | {{icons8-rj45v6-48.png? |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 209: | Line 202: | ||
== Specific information for Subnet V4 creation == | == Specific information for Subnet V4 creation == | ||
- | {{icons8-subnet-48.png | + | {{icons8-subnet-48.png? |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 222: | Line 215: | ||
== Specific information for Subnet V6 creation == | == Specific information for Subnet V6 creation == | ||
- | {{icons8-subnetv6-48.png | + | {{icons8-subnetv6-48.png? |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 235: | Line 228: | ||
== Specific information for Subnet update == | == Specific information for Subnet update == | ||
- | {{icons8-subnet-48.png | + | {{icons8-subnet-48.png? |
- | {{icons8-subnetv6-48.png | + | {{icons8-subnetv6-48.png? |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 249: | Line 242: | ||
== Specific information for Subnet release == | == Specific information for Subnet release == | ||
- | {{icons8-subnet-48.png | + | {{icons8-subnet-48.png? |
- | {{icons8-subnetv6-48.png | + | {{icons8-subnetv6-48.png? |
^ Name ^ Type ^ Mandatory? | ^ Name ^ Type ^ Mandatory? | ||
Line 269: | 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 }} | + | {{ 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 }} | + | {{ classcreate_iprequest23x.png? |
Line 282: | 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_iprequest.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 293: | 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 }} | + | {{ classassign_iprequest3x.png? |
< | < | ||
Line 313: | Line 306: | ||
</ | </ | ||
- | {{ classprocess_iprequestipcreation13x.png }} | + | {{ classprocess_iprequestipcreation13x.png? |
- | {{ classprocess_iprequestipcreation23x.png }} | + | {{ classprocess_iprequestipcreation23x.png? |
< | < | ||
Line 340: | Line 333: | ||
</ | </ | ||
- | {{ classprocess_iprequestsubnetcreation.png }} | + | {{ classprocess_iprequestsubnetcreation.png? |
Once the subnet is selected, pressing the " | Once the subnet is selected, pressing the " | ||
Line 368: | 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 }} | + | {{ classdetails_ipv4subnet3x.png? |
- | {{ classdetails_ipv6block3x.png }} | + | {{ 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 }} | + | {{ lifecycle_iprequest3x.png? |
===== IP Portal ===== | ===== IP Portal ===== | ||
- | The IP Request management module works in conjunction with TeemIp portal, named IP Portal, that is embedded in the extension since revision 2.5.1. Please, refer to the [[2_x: | + | The IP Request management module works in conjunction with TeemIp portal, named IP Portal, that is embedded in the extension since revision 2.5.1. Please, refer to the [[2_x: |
< | < |