Custom Query (73 matches)
Results (34 - 36 of 73)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#42 | wontfix | Work flow for sharing task numbers | ||
Description |
With the concept of the maintenance technician entering the task and the production person entering the "fault entry" against that task there needs to be a clear work flow for sharing these task numbers. One way to do this would be to reserve a number of tasks (say 5) for a technician and provide a report with the task numbers and space to write down the details. The technician could then print the report and hand the reserved numbers out to production as work comes up. Using the printed report to record the details in the space provided for later entering the "work done" into the task number. The production person would then have a task number to enter their "fault entry" against at any time they wish. Another way to do this would be to make it very easy for the production person to list the "Immediate Callouts" for period and production reference. As these would be the only tasks to which this applies. They would then enter faults against these tasks. The constraint on this would be that all tasks must be entered (with descriptions) before the production person came around to wanting to enter their "fault entries" to produce their production report. Some CMMS systems require the production person to create the task or work order and provide this number to the technician. This often fails since:
For production report see ticket #41. |
|||
#44 | fixed | Check for and correct to ${X.encodeAsHtml()} where required. | ||
Description |
Anywhere that user input is displayed in a page there is the opportunity for html (or worse javascript?) injection. Using ${X} directly renders the text so a user input of "<td>nice</td>" would change the layout of the page. Find and correct all cases to ${X.encodeAsHtml()}. |
|||
#47 | fixed | Filterpane bug when selecting an operator but not inputting a value for ID and Integer attributes | ||
Description |
See bug in grails plugin filterpane: http://jira.codehaus.org/browse/GRAILSPLUGINS-1717 This upstream bug report has been closed and is due for inclusion in filterpane-0.6.5 which has not been released yet. Contributed a further improvement (grails plugin rev 59495) so that user input parsing is done in a type safe way. This is now fixed in grails-filterpane-0.6.6-SNAPSHOT Fixed at r361 by upgrading plugin to the newly release 0.6.6-SNAPSHOT. |