Custom Query (73 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (34 - 36 of 73)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Ticket Resolution Summary Owner Reporter
#36 fixed Store configuration settings in database Gavin Gavin
Description

Create a new AppConfig class.
The system can record events and configuration settings in this class.

e.g:

Class AppConfig {
    String name
    String value
}

This will be used for recording:

  • Base data created, then can be tested to disable double creation.
  • Demo data created, then can be tested to disable double creation.
  • Date formats.
  • and other configuration settings.
#37 fixed Task should have assigned groups along side assigned persons Gavin Gavin
Description
  • Many assignedGroups may be added to a task.
  • Many assignedPersons may be added to a task.
  • A persons tasks would be every task that they are assigned to and every task that any group that they belong to is assigned to and every task where they are lead person.
  • Record changes to assigned groups as modifications see ticjet #35
  • Allow a targetStartDate for the assigned group? No this would then be better as a sub task.
  • The person groups now have the added benefit of acting as a training/qualification record. Since only persons trained/qualified to be in the group are added to that group.

Implemented in r239, r240, r241, r242, r243, r245.

#38 fixed A way to assess and record the condition severity of an asset when performing a preventative maintenance task Gavin
Description

When performing a preventative maintenance task that has a procedure, it would be nice to be able to record the assessed condition of the asset/assembly/component specified in each maintenance action.

In the current configuration a task is the smallest unit that can hold this information.

class ConditionSeverity {
    String code
    String recommendation
}

Base data:

Code-Recommendation
A  - Normal Monitoring
B  - Increase Monitoring
C  - Replace 2-6 weeks
D  - Replace 1-2 weeks

Possibly a 'recorded condition' domain class could be created and used:

class ConditionRecord {
    MaintenanceAction maintenanceAction
    Date dateRecorded
    ConditionSeverity conditionSeverity
}

Recording the condition of each maintenanceAction in the database has been decided against, for now, in favour of recording the worst condition severity against the task. Printing the taskProcedure out and keeping the paper copy will suffice as report and audit trail is supplied by TaskProcedureRevisions.

'Work Performed', 'Part Changed' and 'Part Repaired' are separate conditions that will be indicated by an inventory item used on the task.

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Note: See TracQuery for help on using queries.