For our Domo subscribers we have pretty much added every report that’s been suggested if we have the data to accomplish it.
This will probably not get worked on for anything that is possible in Domo – if you haven’t tried it, I would recommend it – and let us know if there is a report you want.
Making a “report builder” is a major project, which is why we bought Domo even though it’s the most expensive piece of software our company has bought.
This is a must have for any company looking to improve their business and be more successful.
This is totally a no-brainer, except, there are tons of implications. If we allow some HTML, what is the subset? Most of the formatting stuff? colors?
Once colors and sizing is allowed, does that carry through to the mobile view, to the template system?
It would take 5 minutes to put a wysiwyg on the ticket comment – but much much more consideration to do it really well in all the places ticket comments show up.
Keep voting and commenting..
Hey there -
Can you just sign up for a free surveymonkey account and put the link in a Marketr campaign?
My feeling is this already works, and we probably don’t need to build anything
What if any appointment that had a location specified we could calculate the road-miles from your office to there, and put that in a report?
A little simpler than doing real vehicle/person tracking, still gets you pretty good data – and would be more realistic for us to quickly build.
Let me know in the comments..
Thanks for the votes everyone, we have been watching this thread for a while and are only holding off because this seems like it will have to be a really deep/technical integration to provide the right level of value. It will probably take a ton of development time away from big things like QuickBooks/Xero integrations. We just need to wait for the right time.
Planned means we want to do it, not that it’s scheduled for a dev to work on yet.
We just scheduled a few tasks that had 70+ votes, we can’t do this before those.
I would like to see this as an option.
I think there should be a classification for issues to mark them as contract or breakfix issues. If it's a contract issue then the hours worked are simply deducted from the contract hours and invoicing independently for that issue is not necessary. The reoccurring invoice stays static at the original agreed price. If there are more hours used than initially prepaid then a seperate invoice is generated for those hours at the end of the month. If it is a breakfix issue you can follow the standard repairshopr invoicing model.
In order for this to work the pre-paid hours should be tied to the contract and marking issues as contract deducts from that pool. Our contracts are quarterly and renew quarterly but we invoice monthly.