Le 20/05/2011 15:00, Fabrice Flore-Thebault a écrit :
Hi,
Hi Fabrice, all,
I wish to propose a feature derived from the usage made by some users of the
"Text on the login page" :
They use the text on the login page to report general health of IT services,
and avoid that users report multiple time an incident already known and which
has been finally become a general problem.
Their question was to give more visibility to this element, for instance
putting this text in a warning box. It's only formatting of one page, i guess
it is not a generic need.
But their behaviour made me think about the Problems/Changes work in
progress. Here is the idea :
On the login page, have and area to describe the actual and planned health
state of the IT Services. To achieve this, display a list of selected
problems and changes.
For each problem or change, add a checkbox "make it public".
Maybe also another field : "text to display in the public area".
On the login page, display the list of public problems and changes in a
warning box.
What do you think of this ?
It's a good idea but could I report you suggestions I have following
discussions with IT managers?
Considering an IT infrastructure complexity today there are many
failures that most of the users doesn't even know.
So alerting every user about all events is not exactly the better way
for IT managers to convince them that they have the best IT in the
world. :-)
So this is a good idea but it will be use only in case of general failure.
So another idea would be to have a pop-up alert only in case of ticket
creation on Entity (or sub-entity if recursivity applied) and Category
(or sub-category) concerned by the problem.
So that would suppose to add a check-box under yours:
[] "Alert whenever a new ticket is created relative to this category"
[ TextField to fill with your alert text ]
The alert would stop as long as the checkbox is unchecked in the problem
form.
_______________________________________________
Glpi-dev mailing list
[email protected]
https://mail.gna.org/listinfo/glpi-dev
