It would make sense to me to have a queue for meter readings, where each 
reading is a ticket that’s associated with the meter asset.

Christopher Manly
Coordinator, Library Systems
Cornell University Library Information Technologies

On 12/22/16, 6:53 PM, "rt-users on behalf of StreatsAhead" 
< on behalf of> wrote:

    Hi all,
    I'm trying to make some custom functionality for an asset, I need to
    automatically update the value of one custom field of an asset when another
    custom field on the same asset is changed. I took a look at using scrips but
    couldn't get them to fire when working with assets. I'm now thinking it
    might be better to have a ticket workflow instead. The objective is:
    We have a bunch of water meters, we need to update the readings in RT every
    now and then compile a report at the end of each year.
    A few calculations need to be made on the readings and stored against the
    Could someone point me in the right direction for this project?
    View this message in context:
    Sent from the Request Tracker - User mailing list archive at

Reply via email to