Settings and activity
73 results found
-
7 votes
Ashley Nuttall
supported this idea
·
An error occurred while saving the comment -
13 votesAshley Nuttall
supported this idea
·
-
9 votesAshley Nuttall
supported this idea
·
-
12 votesAshley Nuttall
supported this idea
·
-
6 votesAshley Nuttall
supported this idea
·
-
7 votesAshley Nuttall
supported this idea
·
An error occurred while saving the comment Ashley Nuttall
commented
I struggle to understand the point that a user is be able to assign a PMP to and Asset/Location without a step. What exactly does this achieve for the client? Maybe when we was managing WO's but now almost all PM management is now a WR' level. This just causes support calls and issues.
-
5 votesAshley Nuttall
supported this idea
·
-
6 votes
An error occurred while saving the comment Ashley Nuttall
commented
I think that all timestamps (start/stop) should be at least asked to add a comment. I agree that it would be a good idea to have a check box to send the comments as an email notification to the supervisor and/or Requester
-
23 votes
An error occurred while saving the comment Ashley Nuttall
commented
Enzo - This does exist but need to watch the formatting of the messages text, this does need a little bit of work to make it work complete
-
20 votesAshley Nuttall
supported this idea
·
-
26 votesAshley Nuttall
supported this idea
·
-
11 votesAshley Nuttall
supported this idea
·
-
7 votesAshley Nuttall
supported this idea
·
-
92 votesAshley Nuttall
supported this idea
·
-
58 votesAshley Nuttall
supported this idea
·
An error occurred while saving the comment Ashley Nuttall
commented
We often get issues with lost WR's or WR's that are stuck at a status because of some quirk in the SLA and a change (return or status change) that for whatever reason gets locked and cant be change, by anyone except the requester or sometime no one at all. In most cases this is due to a helpdesk sept log setting. It would be good if a super user could access all WR's and override the issues and adjust the status to get things moving. In many cases this will be to cancel/stop or close but should allow for all other status reset to the matching SLA. The step log should include comments to log the super user intervention.
I also think direct access to the history via the console is a good idea but should be a switch so not to overload the active console and should be controlled by a forced restriction as the hwr table is often holding a large amount of data at the same status.
Along the same lines would be good to have access to the reports like other consoles
-
34 votesAshley Nuttall
supported this idea
·
-
28 votesAshley Nuttall
supported this idea
·
-
13 votesAshley Nuttall
supported this idea
·
-
8 votesAshley Nuttall
supported this idea
·
-
6 votesAshley Nuttall
supported this idea
·
the problem with this is the account code could come from multiple wr criteria which i believe is why to date this has not been auto populated. However i think this could be controlled by a application parameter to set the default account code by a set field i.e. wr.bl, or wr.requestor which can then be changed if required.