Documentation

User Tools

Site Tools

Trace:
extensions:teemip-request-mgmt

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
extensions:teemip-request-mgmt [2025/07/02 14:34] – cnaudextensions:teemip-request-mgmt [2026/04/20 18:42] (current) – [Revision History] cnaud
Line 31: Line 31:
 ===== Revision History ===== ===== Revision History =====
 ^  Version  ^  Release Date  ^  Status  ^  iTop \\ Min  ^  IPAM for iTop \\ Min  ^  Comments  ^ ^  Version  ^  Release Date  ^  Status  ^  iTop \\ Min  ^  IPAM for iTop \\ Min  ^  Comments  ^
-|  **3.2.0**  |  2025-07-02  |  Supported  |  3.2.0  |  3.2.0  | - Implement iTop Portal new look \\ - Replace legacy CRUD methods by new CRUD events  |+|  3.2.1  |  2026-05-02  |  Supported  |  3.2.0  |  3.2.0  | - Update portal logo  | 
 +|  **3.2.0**  |  2025-07-02  |  Supported  |  3.2.0  |  3.2.0  | - Add Brazilian translation \\ - Implement iTop Portal new look \\ - Replace legacy CRUD methods by new CRUD events  |
 |  3.1.2  |  2024-08-14  |  Supported  |  3.0.0  |  3.1.0  | - TeemIp / iTop 3.2 and PHP 8.3 compatible version | |  3.1.2  |  2024-08-14  |  Supported  |  3.0.0  |  3.1.0  | - TeemIp / iTop 3.2 and PHP 8.3 compatible version |
 |  3.1.1  |  2023-12-11  |  Obsolete  |  3.0.0  |  3.1.0  | - Add Chinese (simplified) translation | |  3.1.1  |  2023-12-11  |  Obsolete  |  3.0.0  |  3.1.0  | - Add Chinese (simplified) translation |
Line 91: Line 92:
 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 ?nolink }}+{{ details_menu_iphelpdesk3x.png?nolink }}
  
 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 101: Line 102:
   * The number of Open IP requests, grouped by organization.   * The number of Open IP requests, grouped by organization.
  
-{{ dashboard_iprequests.PNG ?nolink }}+{{ dashboard_iprequests.PNG?nolink }}
  
 ===== IP Request ===== ===== IP Request =====
  
-{{iprequest.png  ?nolink}}+{{iprequest.png?nolink  }}
  
 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 142: Line 143:
 == Specific information for IP address V4 creation == == Specific information for IP address V4 creation ==
  
-{{icons8-rj45-48.png  ?nolink }}+{{icons8-rj45-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 161: Line 162:
 == Specific information for IP address V6 creation == == Specific information for IP address V6 creation ==
  
-{{icons8-rj45v6-48.png  ?nolink }}+{{icons8-rj45v6-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 180: Line 181:
 == Specific information for IP update == == Specific information for IP update ==
  
-{{icons8-rj45-48.png  ?nolink }} +{{icons8-rj45-48.png?nolink }} 
-{{icons8-rj45v6-48.png  ?nolink }}+{{icons8-rj45v6-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 193: Line 194:
 == Specific information for IP release == == Specific information for IP release ==
  
-{{icons8-rj45-48.png  ?nolink }} +{{icons8-rj45-48.png?nolink }} 
-{{icons8-rj45v6-48.png  ?nolink }}+{{icons8-rj45v6-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 202: Line 203:
 == Specific information for Subnet V4 creation == == Specific information for Subnet V4 creation ==
  
-{{icons8-subnet-48.png  ?nolink }}+{{icons8-subnet-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 215: Line 216:
 == Specific information for Subnet V6 creation == == Specific information for Subnet V6 creation ==
  
-{{icons8-subnetv6-48.png  ?nolink }}+{{icons8-subnetv6-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 228: Line 229:
 == Specific information for Subnet update == == Specific information for Subnet update ==
  
-{{icons8-subnet-48.png  ?nolink }} +{{icons8-subnet-48.png?nolink }} 
-{{icons8-subnetv6-48.png  ?nolink }}+{{icons8-subnetv6-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 242: Line 243:
 == Specific information for Subnet release == == Specific information for Subnet release ==
  
-{{icons8-subnet-48.png  ?nolink }} +{{icons8-subnet-48.png?nolink }} 
-{{icons8-subnetv6-48.png  ?nolink }}+{{icons8-subnetv6-48.png?nolink }}
  
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
Line 262: Line 263:
 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?nolink }}
  
 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?nolink }}
  
  
Line 275: Line 276:
  
 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?nolink }}
  
 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 287:
 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?nolink }}
  
 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?nolink }}
  
 <note> <note>
Line 306: Line 307:
 </note> </note>
  
-{{ classprocess_iprequestipcreation13x.png ?nolink}} +{{ classprocess_iprequestipcreation13x.png?nolink }} 
-{{ classprocess_iprequestipcreation23x.png ?nolink}}+{{ classprocess_iprequestipcreation23x.png?nolink }}
  
 <note> <note>
Line 333: Line 334:
 </note> </note>
  
-{{ classprocess_iprequestsubnetcreation.png ?nolink}}+{{ classprocess_iprequestsubnetcreation.png?nolink }}
  
 Once the subnet is selected, pressing the "Process" button will create the subnet in the data base with the attributes set in the request. At the same time, the ticket is put in the Resolved state. Once the subnet is selected, pressing the "Process" button will create the subnet in the data base with the attributes set in the request. At the same time, the ticket is put in the Resolved state.
Line 361: Line 362:
 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 "**Allow automatic subnet creation**" / "**Allow automatic IP creation**" added to the subnet blocks and subnets. Default is "yes". 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 "**Allow automatic subnet creation**" / "**Allow automatic IP creation**" added to the subnet blocks and subnets. Default is "yes".
  
-{{ classdetails_ipv4subnet3x.png ?nolink}}+{{ classdetails_ipv4subnet3x.png?nolink }}
  
-{{ classdetails_ipv6block3x.png ?nolink}}+{{ classdetails_ipv6block3x.png?nolink }}
 ===== 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?nolink }}
  
  
extensions/teemip-request-mgmt.1751466887.txt.gz · Last modified: by cnaud

Page Tools