You are not logged in.
Pages: 1
Hello every one!
I try to add a new ticket status in GLPI via this instruction http://blog.angel2s2.ru/2009/04/glpi_27.html (It's Russian language you can translate it via google translate) It instruction works only for GLPI ver 0.71.5 only, and I can't add status via this method in GLPI v 0.84.
May somebody help me to solve this problem?
Offline
I did something similar the other day. I didn't create a new status but I reuse some of the ones are already included.
There is an array for the status in /inc/commonitilobjet.class.php (lines 64 and up).
Now you need to edit the /inc/ticket.class.php (lines 2346 and up) to add the new names for the statuses you want to add
Please remember here you are not creating new statuses, you are just repurposing some of them.
Hope it helps.
Last edited by alexian (2014-07-28 20:05:27)
Alexian,
______________________________________
In the process of learning. One bit at the time!..
______________________________________
Offline
Hello! Thank you for your advance, it's very helpful!
I found status code on line 2616 in ticket.class.php
I add new status string in code:
// To be overridden by class
$tab = array(self::INCOMING => _x('ticket', 'New'),
self::ASSIGNED => __('Processing (assigned)'),
self::PLANNED => __('Processing (planned)'),
self::WAITING => __('Pending'),
self::SOLVED => __('Solved'),
self::CLOSED => __('TEST'),
self::CLOSED => __('Closed'));
But it's dont work? when I create new ticket I dont see new status in form.
Where is my fault?
Thanks for advance!
Offline
Hi mercury131,
The problem is that you are using the object CLOSED two times. You need to use another from the commonitilobject array:
// STATUS
const INCOMING = 1; // new
const ASSIGNED = 2; // assign
const PLANNED = 3; // plan
const WAITING = 4; // waiting
const SOLVED = 5; // solved
const CLOSED = 6; // closed
const ACCEPTED = 7; // accepted
const OBSERVED = 8; // observe
const EVALUATION = 9; // evaluation
const APPROVAL = 10; // approbation
const TEST = 11; // test
const QUALIFICATION = 12; // qualification
Use any of the other and you'll be able to see it in the status dropdown list.
Cheers,
Last edited by alexian (2014-07-28 20:05:49)
Alexian,
______________________________________
In the process of learning. One bit at the time!..
______________________________________
Offline
Such will just break GLPI.
Each status is associated with code and rule.
Adding new constants will not work, and will result in strange behavior.
Dév. Fedora 29 - PHP 5.6/7.0/7.1/7.2/7.3/7.4 - MariaDB 10.3 - GLPI master
Certifié ITILv3 - RPM pour Fedora, RHEL et CentOS sur https://blog.remirepo.net/
Offline
Ok remi, I agree but as one of the main developers how will you solve this issue?
Sometimes we need a new status.
What should we do?
Alexian,
______________________________________
In the process of learning. One bit at the time!..
______________________________________
Offline
Hey,
does this means that every software update will revert my changes to original status? This will make me crazy!
Why don't use a db table to store status?
Thanks
Offline
For me, it's a good solution!..
Hey,
does this means that every software update will revert my changes to original status? This will make me crazy!Why don't use a db table to store status?
Thanks
Offline
So... should I hope to see this enhancement in next release?
Offline
Hi everyone. It would be a very great feature, bur it seems lastest stabel version don't have this.
Offline
hello everyone,
watch this it might be helpful even for GLPI 10.
link : https://www.youtube.com/watch?v=tlZ9Kitr2Uw
regqrds
Last edited by k.iazza (2022-02-06 01:06:24)
Offline
...watch this it might be helpful even for GLPI 10....
Hello, link is unavailable. Could you share it again?
Offline
Pages: 1