Welcome to the Alloy Ideas Portal đź‘‹ Here, you'll be able to browse improvement ideas raised by our community, vote on ideas you agree with or even raise your own ideas. We review all ideas raised and we endeavour to respond to all raised ideas.
Any ideas submitted will be immediately visible on the portal for others to vote on, please do not include anything in your ideas you do not wish to be shared with others.
Sure - this would apply to create and edit actions mainly, the view action might complicate things. It could be the same time offset mechanic as what we see in the AQS builder or in workflows.
2 potential uses for this in our setup:
Tracking creation time without using itemsMetaData - there are things like files and custom reports where we want to be able to track when an item was created, but have no interest in who created it or further updates to the item. We also don't want to add extra work for the system by implementing itemsMetadata and all its additional functions. Having a timeoffset of 0 minutes against a "Created Time" attribute would allow us to use AQS to interrogate items chronologically rather than trawling through item logs.
tasks that don't need priorities - for example, we have footway hand salting jobs which should always be completed within 1 working day. There are no exceptions to this rule within this design. So, rather than relying on manual entry or a workflow to populate that target time, it could be facilitated within the item form
Cheers,
Aaron
Hi @Guest
Thanks for raising this one with us. Are you able to give a bit more information on this idea? I just want to understand the requirements a bit more on this one.
Thanks,
Andy