﻿__group__	ticket	summary	component	version	milestone	type	owner	status	created	_changetime	_description	_reporter
Active Tickets	84	Implement inital purchase order pdf's of inventory reorder and purchases search views.	gnuMims - application general	trunk	0.8 - Purchasing and Inventory Improvements	enhancement		new	2010-09-24T20:35:55+10:00	2010-10-27T15:01:09+10:00	"The purchases pdf is essentially a purchase order since the supplier, this company (address etc) and items to be purchased are known.

The reorder view can be used to generate a ""Quote Request"" pdf.

These pdf's can be reused later when ticket #30 is implemented."	Gavin
Active Tickets	88	Implement Regulatory Task Completion on Equipmet Register Report OH&S	gnuMims - application general	trunk	0.9 - General Improvements	enhancement		reopened	2010-10-27T15:45:39+10:00	2010-11-24T15:41:35+10:00	"Regulatory Task Completion needs to be reported for assets that have regulatory requirements.

 * This may require a new flag on the asset, also see ticket #22.
 * There is a text extended attribute that should be retained.
 * Result example: 50% (5/10)
 * A date range will now also be required for this report."	Gavin
Active Tickets	30	Implement purchase orders	gnuMims - application general	trunk	0.8 - Purchasing and Inventory Improvements	enhancement		new	2009-11-11T20:42:44+10:00	2009-12-18T15:13:19+10:00	"Each purchase order can only be made out to a single supplier so this could be linked to from inventory items with a 'puchase from this supplier' link. This would then start a purchase order.

On receipt of items they should be easily credited into inventory with automatic creation of inventory movements and a payment approved action is required.

Purchase order events:
 * Ordered.
 * Received partial.
 * Received complete.
 * Invoice approved (approved for payment, auto on received complete?)
 * Payment made.

Purchase order numbers are supplied in batches eg P10001 - P20000 an interface and logic is required to handle this.

{{{
class PurchaseOrder {
    PurchaseOrderNumber purchaseOrderNumber
    Integer estimatedTotal
    hasMany = [purchaseOrderLineItems: PurchaseOrderLineItem]
}

class PurchaseOrderNumber {
    PurcaseOrder purchaseOrder
    String value
}

class PurchaseOrderLineItem {
    InventoryItem inventoryItem
    CostCentre(Department.costCode+SystemSection.costCode?)
    CostCode from asset type or asset.
}
}}}"	Gavin
Active Tickets	87	"Implement ""Order on Hold"" feature on reorder search view."	gnuMims - application general	trunk	0.8 - Purchasing and Inventory Improvements	enhancement		new	2010-10-27T15:09:27+10:00	2010-10-27T15:09:27+10:00	This allows a purchaser to mark items on reorder list as orderOnHold=true to indicate that this item should not be reordered at this time. The quote request pdf would also not show these items. The only audit requirement at this stage is a person and date stamp.	Gavin
Active Tickets	106	PM Entry time not being counted in Reactive Ratio report	gnuMims - application general	trunk	0.9 - General Improvements	defect	Gavin	new	2014-06-23T18:48:19+10:00	2014-06-23T18:48:19+10:00	On task with a procedure the PM Entry time is not being counted on the Reactive Ration report.	Ross Challinor
Active Tickets	66	Feature request: Calendar view to shown assignedGroup totals	gnuMims - application general	trunk	0.9 - General Improvements	enhancement		new	2010-05-28T17:08:43+10:00	2010-10-27T15:26:20+10:00	"Currently the task calendar view is not particularly useful due to the shear number of tasks on each day. Even with filtering showing the tasks on the calendar actually provides less information than the list view.

However displaying the assignedGroup and perhaps assignedPerson hh:mm totals on the calendar may prove very usefull."	Gavin
Active Tickets	82	Ability to select task assets from asset tree	gnuMims - application general	trunk	0.9 - General Improvements	enhancement		new	2010-08-01T21:06:40+10:00	2010-08-01T21:06:40+10:00		Gavin
Active Tickets	92	Working Shift feature required	gnuMims - application general	trunk	0.9 - General Improvements	enhancement		new	2010-10-28T14:17:18+10:00	2010-10-28T14:23:35+10:00	"Currently the taskGroup is used as ""Electrical Dayshift"", ""Electrical Nightshift"". This should factored out into a WorkingShift table and a task.workingshift field should then be used for this assignment.

When a person logs in they should be able to select their current shift and see only those logs. 

{{{
class WorkingShift {
    @indexed // Is auto indexing available?
    String ref // A constant used for lookup, e.g: dayshift.
    String name // Language free, e.g: Dayshift, Nightshift.
    String description = """"
    Integer startHour = 0 //24hr format, e.g:06
    Integer startMinute = 0 //24hr format
    Integer finishHour = 0 //24hr format, e.g:18
    Integer finishMinute = 0 //24hr format
    Integer startFinishMarginHour = 2 //margin in hours.
}
}}}"	Gavin
Active Tickets	95	New yellow pendingResolution flag on Tasks	gnuMims - application general	trunk	0.9 - General Improvements	enhancement		new	2010-11-18T16:32:07+10:00	2010-11-23T08:07:25+10:00	"Currently a red flag is used for attentionFlag, a yellow attention read/noted/hold flag would be nice too. Or another group to put holding flags in.

New modifications will also be required.
New dynamic task search ""New Flag's"" and ""Pending Resolution""

Secondly require a work done entry when clearing flags."	Gavin
Active Tickets	102	"Security regression tests for bypass by adding "".html' to the URL"	gnuMims - application security	trunk	0.9 - General Improvements	enhancement		new	2011-05-02T07:19:14+10:00	2011-05-02T07:20:57+10:00	"Add regression functional tests as per ticket #98 and r888.

These include testing GET url's which the logged in user should not have access to, by appending to the url ('index.', 'index.html', 'index.xml', 'index..', 'index.gsp', 'index/index' etc)."	Gavin
Active Tickets	79	Reminder: Test CSV import functions and stop/start searchable index	gnuMims - application general	trunk	0.x - Future	defect		new	2010-07-14T15:45:17+10:00	2010-11-25T14:11:10+10:00	"Several changes have happened in the last few milestones that may require small adjustments to the CSV import functions. There is also a new CSV grails plugin that may be of interest. Tests should be written if possible.

Inventory import function improved in r721 - turn off searchable index mirroring during import and manually tested."	Gavin
Active Tickets	32	Show only the non-detailed controllers in 'admin' view	gnuMims - application general	trunk	0.x - Future	enhancement		new	2009-11-11T20:58:31+10:00	2009-12-16T12:12:34+10:00	Should be able to use the grep taglib or a controller regex to do this.	Gavin
Active Tickets	34	Task overdue/warning flag	gnuMims - application general		0.x - Future	enhancement		new	2009-11-17T09:30:59+10:00	2010-10-27T15:35:48+10:00	"Concept idea: overdue/warning flag for tasks that are overdue by priority and target start date. This flag should be automatically set by the system.

 * Target dates are targetStart and targetCompletion.
 * !TaskPriority#overdueIn may be 1=24hr, 2=48hr, 3=72hr (3 shifts), 4=none.
 * See also ticket #22 for priority sourced from the primaryAsset.

"	Gavin
Active Tickets	40	Feature to assemble a 'work order' from task	gnuMims - application general	trunk	0.x - Future	enhancement		new	2009-11-24T15:15:22+10:00	2009-12-18T14:52:53+10:00	"Tasks are great but some work flows are based around work orders.
An pdf button that creates a work order from the task, procedure and sub tasks would be nice to have."	Gavin
Active Tickets	41	Production report from fault entries	gnuMims - application general	trunk	0.x - Future	enhancement		new	2009-11-24T15:33:09+10:00	2011-02-28T21:16:55+10:00	"If a production person entered faults against tasks then these faults could be assembled into a production report simply all tasks with ""Immediate Callout"" and that production reference would be the production report for that production."	Gavin
Active Tickets	43	Base type domain classes should have caching enabled	gnuMims - application general	trunk	0.x - Future	enhancement		new	2009-11-28T11:07:16+10:00	2009-12-18T14:55:07+10:00	"The '*Type' classes that don't change often should have caching enabled to improve performance.
 * Period
 * !TaskType
 * etc

To turn on hibernate second level caching for these classes do something like:
{{{
static mapping = {
	cache true
}

or limit caching to non-lazy:
cache usage:'read-write', include:'non-lazy'
}}}
"	Gavin
Active Tickets	46	Reminder: Check for optimistic locking in edit views	gnuMims - application general	trunk	0.x - Future	enhancement		new	2009-12-01T01:17:31+10:00	2010-11-24T15:23:33+10:00	Check and ensure that optimistic locking is in the edit views and that it is working.	Gavin
Active Tickets	56	An improved way to assign a parent to an existing task is required	gnuMims - application general	trunk	0.x - Future	enhancement		new	2009-12-24T13:21:35+10:00	2009-12-24T13:58:21+10:00	"Removed/commented out the ability to change the parent task in r246, since this currently just lists all tasks and becomes very slow with larger task numbers.

The ability to assign a parent to an existing task may not be immediately required but certainly would be good to have.

At the very least the !TaskService.possibleParentList needs to be smarter and not return ALL tasks."	Gavin
Active Tickets	60	Make the asset tree more flexible by changing Section to self referencing	gnuMims - application general	trunk	0.x - Future	enhancement		new	2010-03-16T22:28:56+10:00	2010-03-17T09:53:15+10:00	"This is a very good idea and would make the asset tree depth that extra bit more flexible. This could be setup similar to the way an Asset can have as many depths of Sub Items as required.

Example:
 * Company
  * Region
   * Site
    * Section

Company and Region are currently not catered for, while Section already has a Department.

This affects:
 * Database schema.
 * Asset tree taglib as accessed from the tree icon on the main nav.
 * The asset tree import and export functions.
 * Cascase deletion and updates.

Hence placing in future milestone for now."	Gavin
Active Tickets	89	Contractor management	gnuMims - application general	trunk	0.x - Future	enhancement		new	2010-10-27T15:55:05+10:00	2010-10-27T15:55:54+10:00	There is a Service inventory type and supplier (new service type for supplier?). Service info pack could be added/linked to one of these. The pack would contain audit info on inductions and insurance expiry dates. This info would be used to raise an overdue warning.	Gavin
Active Tickets	94	Inventory item audit with expiry	gnuMims - application general	trunk	0.x - Future	enhancement		new	2010-11-16T13:22:45+10:00	2010-11-16T13:22:45+10:00	"To update inventory item data (e.g. recommended reorder levels).

Currently a continuous cycle of review is used for any inventory item that is accessed.

This could be improved by implementing an Inventory audit with expiry feature. This is most valuable when the reordering is done by administration staff."	Gavin
Active Tickets	103	Labour Utilisation reports	gnuMims - application general	trunk	0.x - Future	enhancement		new	2011-06-30T16:19:22+10:00	2011-06-30T16:19:22+10:00	"Labour Utilisation is very useful management information.
 * A report similar to the Reactive Ratio report layout with blue in place of the amber wedge for Non Preventative.
 * A report similar to the Reactive Ratio report layout with total Labour Utilisation = Preventative + Scheduled + Unschedulded + Immediate + Project + '''Unused'''"	Gavin
Active Tickets	19	Investigate CI and testing frameworks	Tserver - server admin	trunk	0.x - Future	task		new	2009-05-27T15:02:05+10:00	2011-04-06T03:54:44+10:00	"Find, analyse and start to implement a testing framework.

We currently have a script based continuous build on svn commit (this was disabled due to VPS load). The build is now manually triggered using the same scripts.

Try trac-bitten CI as it is now in Debian Squeeze.
http://bitten.edgewall.org/wiki/Documentation/install.html"	Steven
Active Tickets	58	Reminder: check for and correct to ${X.encodeAsHtml()} where required.	gnuMims - application general	trunk	0.x - Future	task		new	2009-12-28T01:39:42+10:00	2009-12-28T01:39:42+10:00	"This is a reminder for the original ticket #44.

This reminder is to ensure ongoing vigilance in this area."	Gavin
Active Tickets	45	Make dataFormat a global in Config.	gnuMims - application general	trunk	0.9 - General Improvements	enhancement		new	2009-11-28T12:41:43+10:00	2010-08-01T21:01:28+10:00	"In Config.groovy place a global.dateFormat='EEE, dd-MMM-yyyy'.

Then find and replace all cases of the string with the global variable:
 * ${grailsApplication.config.global.dateFormat}
 * or
 * import org.codehaus.groovy.grails.commons.*
 * !ConfigurationHolder.config.global.dateFormat"	Gavin
Active Tickets	73	Change primary/associated assets	gnuMims - application general	trunk	0.9 - General Improvements	enhancement	Gavin	new	2010-06-11T13:01:32+10:00	2010-08-01T21:09:37+10:00	Only require multiple assets. Multiple assets may be added to a task, primary/associated differentiation not required.	Ray Smith
Active Tickets	61	Rotable equipment management	gnuMims - application general	trunk	0.x - Future	enhancement		new	2010-03-27T00:12:28+10:00	2010-11-24T15:20:31+10:00	"Most of the 'big' CMMS systems have rotable equipment/inventory management. This could be as simple as location tracking or include full overhaul reports, repair specs/procedures, history of cost, quote, repair details, failure intervals. ID Tags, stamps, barcodes, data dot and even RF ID chips may be used to id equipment.

This is a wish list item as rotable management is an advanced maintenance practise and even large companies struggle with it, since gnuMims is aimed at mid-size sites, there may be minimal call for this feature.

The most basic implementation is to have a text field where the item it may be entered on breakdown/repair tasks. A more complete implementation would have inventory items of type rotable and the locations tracked in the asset tree.

The current implementation is to place the equipment id in the task description and assign the task to an asset while using a separate inventory item for repaired. This means the task(s) can be found with minimal effort(2 search fields: asset and description) and repaired inventory item failure rates vs new items can be tracked."	Gavin
Active Tickets	99	Upgrade filterpane plugin to version 2	gnuMims - application general	trunk	0.x - Future	enhancement		new	2011-04-29T06:30:38+10:00	2011-04-29T06:30:38+10:00	"Many enhancements, upgrade info:
http://www.grails.org/plugin/filterpane"	Gavin
Active Tickets	100	Upgrade acegi plugin to spring-security-core	gnuMims - application general	trunk	0.x - Future	enhancement		new	2011-04-29T06:33:27+10:00	2011-04-29T06:33:27+10:00	"Acegi plugin is obsolete.

Upgrade section in docs:
http://www.grails.org/plugin/spring-security-core"	Gavin
Active Tickets	101	Upgrade jasper plugin	gnuMims - application general	trunk	0.x - Future	enhancement		new	2011-04-29T06:39:20+10:00	2011-04-29T06:39:20+10:00	"Jasper-1.2.1 plugin uses Grails-1.3.0 > * and Jasper-4.0.0

http://www.grails.org/plugin/jasper

Jasper 4 is a big improvement in the jasperserver but apparently not a major api change for the jasper lib report engine. 

Therefore upgrading reports should not be too hard. In the past I have had success with simply opening the report with iReport of the correct version and saving.
"	Gavin
Active Tickets	104	Best Practise figures should appear next to actuals on reports.	gnuMims - application general	trunk	0.x - Future	enhancement		new	2011-06-30T16:38:26+10:00	2011-06-30T16:38:26+10:00	"Best Practise figures are well known for many reports.

These can easily be included in reports, along side the actuals.
 * Reactive Ratio: 85% Preventative to 15% Reactive(Immediate Callout)
 * Utilisation: 20% Unused etc
 * Completion Rate."	Gavin
Active Tickets	33	Fault entries and work requests.	gnuMims - application general	trunk	0.x - Future	enhancement		new	2009-11-17T09:07:30+10:00	2010-11-24T15:10:15+10:00	" * Fault entries are basic entries from the customer reporting a fault.
 * This fault or work request would be non-critical otherwise a callout would have occurred instead.

 * One way to do this would be to have a standing task that fault reports can be made against. These could then be moved to an appropriate task or a new task created for the fault.
 * A better way is to create a task when the fault is entered and populate the task description either from an entry field or the fault."	Gavin
