Marco Gaiarin a écrit :
I've worked a bit to port data from my irm installation (1.3.X, highly
customized) to my glpi 0.4 test installation.

Port seem very easy, most of the tables have the same schema, the
boring work are at most moving from a descriptive field (location =
'Primo Piano') to an id-based filed.


For making the port I suggest taking an older version of GLPI, were the table schema is most the same as irm's, then making the GLPI update which is working from the first public version to the last.

But i've found some drawbacks, and i think some bugs.

1) irm have 6 state, glpi only two (new and old). I miss really other
states, irm use new, old, complete (work done), wait (waiting for
something), assigned (job assigned to someone), active (job on active
processing).
I think that can be added a table like:

id              name            color   open    close
-----------------------------------------------------
new             New             green   X
old             Closed          black           X
complete        Completed       black           X
wait            Wait            red
assigned        Assigned        yellow
[...]
archive         Archive         gray    X       X

and alter the code so we can get status from this table, display as
long name (possibly translated), color if needed and we can also manage
start and stop state in a very simple way.
With this setup we can add as many status as needed.



Actually there are 3 states on GLPI : New (not assigned), Assigned and Old.
For us it seems to be enough and permit to keep daily management easy to use. But we added today a new concept that permit to assign a tracking to a category, in order to permit some peoples to manage some hardware independant Tasks, in that way, having new states could be interresting, but it should be dynamic, we'll think at it... We have a lot of thinks to do before closing the 0.5 release version, so... not sure it'll be on it.


2) my custom irm display priority as strings, not numbers...
as above we can use a table like:

id      name            color
-----------------------------
1       Very Low        gray
2       Low             blue
[...]


3) Also, i think that priority have to be changeble... in a real,
iso9000-like environment that use glpi, if the request are marked
urgent, this imply that have to be solved within a predefined time.
So, for me, Admin/tech users have to be able to lower (for this
example) priority.
It is not feasable to do in mysql prompt, for the tech and for the
user. ;)



(answering points 2 and 3).

We agree that priority management is most basic as it can be, actually, we'll also think on new style and thinks to make it better.
Thanks for the ideas we keep it somewhere near.


4) [for the same reason...] my custom irm add some ``automated followup''
to followups when someone change assegnee or priority. Some sort of raw
like ``user changed priority from X to Y'', or ``user (re)assign job to
UserX''.


This feature is already released in the 0.42 version.


5) i've not very clear how software license handling work... in irm an
instalation are linked both to a license and to a software, so if a
software have no license, still can be installed.
I don't think this is good, but i've found in moving software data the
worst trouble... and something misses.

If i add a licence to a software, they ask me the key (free for free
software), the number (i suppose the number of installable licences)
and the end date that i don't mind.
But... why the number are only limited to 100? Where are saved this
number? I've looked all glpi table and i've not found it.
Using ``free' for free software are merely a praxis or alter the
functionality of the program?

Again, we have a ``forfait'' contract with Micro$oft (a local italian
subsidiary/reseller) that permit us to upgrade/downgrade all M$ OS >=
win95 as we need, and permit us to install most of M$ software as we
need.
Ok, i can put ``Microsoft Office XP Professional'' as a number 100
licences (but is still a bit low...), but i've a box full of win98SE
and win xp home licence, and in the computers i've installed win xp
pro.
I can put also win xp pro as a 100 licence key, but really i've no one
win xp pro licence, only the rights to upgrade other M$ OS...
[in irm now the win xp pro licence key are set to 0 licence to remember
me that i cannot consider it installable standalone...]

Again, i think that in licence could be aded a flag for licence
stickers (if the sticker are stick on a computer or not).


We added a new type of licence that it called "Global", or "forfait licence" this may answer to this needing.

Why "only" 100 licences in a time, because we don't know any structures that buy more than 100 alone licences for a soft in the same time.

Also, we don't want to have the guinness book award for the bigest <select> in an web application. If you want more than 100 licenses you have just to enter again the same serial.

For the stickers, OEM licences and updates licences will appear onto the 0.5 version.


6) i think that job have to be assigned only to admin/tech, not to all
people. Now in tracking if i try to change assegnee, the all user list
pop down.

It's a bug... but we tried and it's unreproductible on our configurations and you're the first who report it, can give us your version and your configuration (php version,web server, os ...). Before have much tests, because we've look at the code recently and all seems to be good.

Also, if you think about ``commercial'' data, i think have to be added
an account type (commercial?) that can alter peripherals data but not
be an assegnee for tracking.


All the rights will be changed for the 0.6 or 0.7 version, it's planned and we're think about how to do that most properly...


I hope to be usefoul, i hope these will be added to upcoming 0.5. ;)


Each user comment us very usefull for us, and permit to have other points of vue than ours, witch is really important, there are good ideas , we'll implement it... on witch version, our free time rate would decide it for us...


--
Bazile
For glpi dev team.


Reply via email to