Add the ability to set DEFAULTS that will auto-populate the fields in a new Asset Service/Asset Maintenance
It would be great if we could enable default settings when creating a new service record. So when I put an asset into maintenance it would automatically populate our desired "Expected Completion Time" of 7 Days and it would auto-populate whomever the preferred vendor is for that type of item or even the preferred vendor for the company. Right now it is kind of annoying to be required to set an "Expected Completion Time" AND a start time because the start time should always be whatever it is currently and we actually do not care about the expected completion date.
If this request is going to take a longer amount of time, then it would be nice for now just to not REQUIRE the expected completion time.

Hi Matthew, thanks for writing in.
While marking an asset into Service, you can just check the “Under Service Indefinitely” checkbox and that will omit the expected return date, putting it into indefinite service. Does that not work for you?
regards
-
You're welcome Matthew!
-
Matthew Foval commented
I just talked with my team and we came up with a more preferred feature request that we want which is a little different than this one. I will go ahead and make a new idea so this one can be ignored. Thanks for your response though.
-
Matthew Foval commented
That is what we have been doing, but it would be nice to have a predefined amount of time that a service request should take so that way if our average service time is 7 days, and we set the default time to 14 days, we would still get a notification on the 15th day that the service is taking longer than expected. Currently we set it to be in service indefinitely and we may not notice the service is taking too long until 21 days or MORE.
Additionally, we send 98% of our assets to be serviced by the same vendor, so if we could set a default service vendor too that would be great.
And while we're talking about this, we may even want to set it to create a Zendesk ticket by default, although I don't know if we would use this or not yet because we are still new to that integration, but we are thoroughly enjoying it.