It would be beneficial to create custom user profiles in GLPI based on departments and assign permissions to different entities.

(This example is very simplified)

Example:

1. User Profiles:

   • IT Department
   • HR Department
   • Finance Department
   • Marketing Department

2. Permissions:

   • Tickets
   • Assets
   • Projects

3. Entities:

   • IT Entity
   • HR Entity
   • Finance Entity
   • Marketing Entity

Permission Matrix:

Collaborative Projects:

Explanation:

• IT Entity: IT and Finance departments collaborate on Project A.
• HR Entity: HR and Marketing departments collaborate on Project B.
• Finance Entity: IT, Finance, and Marketing departments collaborate on Project C.
• Marketing Entity: Marketing, HR, and IT departments collaborate on Project D.

Benefits:

• No need to switch profiles.
• All information is available in one view.
• Users see only the departments and entities where they have permissions.
• Simplifies workflow and improves efficiency.
• Enhances collaboration by allowing multiple departments to share permissions within the same entity.

With templates, you can set rules for defining items like tickets or assets. Applying this to profile customization in GLPI allows users to work within the full structure of the root entity but only see departments and entities where they have permissions. This avoids the need to change profiles to work in different departments.

When creating a dashboard, could we possibly be able to integrate "saved search" results as widgets ?
Thanks in advance

Lorsque nous créons des "tableaux de bord" (ou 'dashboard'), peut-on imaginer une possibilité d'intégrer les résultats des "recherches sauvegardées" sous forme de widgets ?
Merci par avance

Please add variables to the ticket template. Such as the time and date in the title and description field

Hello,

I work in a company that uses a purely internal Exchange mail server (no link to the Internet), which is only used for exchanges between employees.

It is configured in GLPI to send notifications by e-mail and this works well.

However, I think it would be great if we could also set up a second mail server (smtp) in GLPI for sending to external mails, so that notifications could also be sent to employee mail addresses outside the company.

This is something I've managed to do with our Exchange server by creating a mail connector specifically dedicated to sending notifications for GLPI. Except that :

- It's absolutely impractical

- It's not reliable (rejection is highly possible once the mail has arrived on the recipient server (hello Google))

- It would be 200 times simpler if GLPI allowed you to specify more than one mail server.

I don't think I'm alone in this, as quite a few system administrators have a hybrid mail system.

Add ability to clone cables to assets cable management.

I suggest adding the option to add a floorplan to graphically show the location of the PCs. I share an example:

The display of pc's in the form of list is great. But I think that an ideal complement would be to provide the application with the ability to visualize the location of the devices on a floorplan.

# glpi

Glpi Deployment on Kubernetes with persistent volumes and SSL certificate

Glpi Prerequisites - WebServer, PHP, Mysql/Mariadb Database.

Glpi Key Directories - /var/www/html/glpi/{config, plugins, marketplace.Files}.

MariadDB - /var/lib/mysql

Prerequisites for deploying GLPI:-

Kubernetes Cluster

Shared Storage for PV (You may also use local storage, but it is not recommended.)

1. Clone above repo - https://github.com/Dineshk1205/glpi.git

$ git clone https://github.com/Dineshk1205/glpi.git

2. Crate MariaDB root password as secret –

$ kubectl create secret generic mariadb --from-literal=mariadb-root-password=xxxxx

3. Create a glpi namespace.

$ Kubectl create ns glpi

4. Extract controller-v1.9.0.tar.gz file

$ tar -xvf controller-v1.9.0.tar.gz

6. Installing the Nginx controller helm is required.

Helm installation –

$curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3

$ chmod 700 get_helm.sh

$ ./get_helm.sh

6. Nginx deployment: -

Switch to ingress-controller directory.

$ cd ingress-nginx-controller-v1.9.0/charts/ingress-controller

7. Create a ingress-controller namespace

$ kubectl create namespace ingress-nginx

8. Run the following command to install the nginx ingress –

$ helm install -n ingress-nginx ingress-nginx -f values.yaml.

9. SSL Certificate Configuration –

Generate a self-signed certificate or use ca certified certificate.

Crate Secret using Certificate key and cert file in glpi namespace

$ kubectl create secret tls glpi-tls --key xx.key --cert xx.crt -n glpi

10. Update the IP address Range in metallb-pool.yaml file based on your network

11. Update host name in ingress.yaml based on your requiremnts

12. Finally, Install MariaDB And glpi

Switch to cloned Directory glpi and run the below command

$ kubectl apply -f .

Check pod status

$ kubectl get pods -A

Once pods are up, check glpi IP to access the GLPI GUI.

$ kubectl get ingress -n glpi

Create DNS records for the above IP ( IP is above ingress IP, and Hostname will be matched with ingress.yaml file hostname).Access GLPU using FQDN.

DB for Configuring the GLPI

In the Kubernetes cluster, check MariaDB IP

$ kubectl get svc

Note down above mariadbsv cluster IP; use IP for connected Glpi.SQL user use root as user and enter a password. (Password created as secret in previous steps)

Hello, dear GLPI-comminity! I wonder, is it possible to make a dark-mode right on the menu up-right, or somewhere else on main screen to easily change it in the evening? Thanks!

it would be great if in project tasks and projects when you assign the status Closed and this is indicated as Finished State, that percentage of the respective task goes to 100%.

If we want to force the User to fill out the Ticket-Type and therefore make it mandatory, there should be an empty value preselected, the same way as it is in Category. As in default GLPI the Type is already prefilled with request or incident.