Announcement

Collapse
No announcement yet.

time spent should not be set – and especially if we can’t do it consistently.

Collapse
X
 
  • Filter
  • Time
Clear All
new posts

    time spent should not be set – and especially if we can’t do it consistently.

    When a ticket is imported from Quotewerks and it has over 24 hours allocated to it then the hours allocated to the Commit CRM ticket are incorrect.

    Could we make the import tool not set the “time spent” value as time Spent cannot exceed 24 hours and therefore the 30 hours value is simply ignored. time spent should not be set – and especially if we can’t do it consistently.

    Re: time spent should not be set – and especially if we can’t do it consistently.

    Yes, we agree, it should probably not set the time spent even for <24 hours entries. Time spent should represent actual work, unlike quoted work. Thanks for your asking. Noted.

    Comment


      Re: time spent should not be set – and especially if we can’t do it consistently.

      okay.. thanks however how do we import QuoteWerks quotes with 40+ hours properly?

      Comment


        Re: time spent should not be set – and especially if we can’t do it consistently.

        The best option at this time would probably be to clear the time spent values from the charges created from QuoteWerks quotes.

        Comment

        Working...
        X