Last Response and Due Date issue: Page 2

Last Response and Due Date issue

KevinTheJedi

Yes that looks correct, if it's still not working then I'm not sure what's going on in your case. Applying the fix and updating the Primary Data Source addressed the same exact issue for me.

Cheers.

caves

Seem like it only happens as the Column is refreshed. Does it use that same code on the refresh? Could it be something with the way it refreshes?

KevinTheJedi

@caves

I don't understand the question. With this fix it should show the actual times; nothing to do with refresh.

Cheers.

caves

Seems like some type of refresh is happening because I can just sit on the page and the minutes will count up in these columns. I am not refreshing the page.

KevinTheJedi

caves

Then you probably have the auto-refresh rate set in your profile. Regardless, it shouldn't show the same Due Date for all tickets unless the tickets were all created at the same time. Seems like you didn't apply the patch correctly or didn't update your Primary Data Source for the field.

Cheers.

caves

AutoRefresh is disabled and as shown above the settings are correct. Same thing happens on both Last Response and Due Date

KevinTheJedi

@caves

I don't know what else to say here. I was able to replicate your issue, I applied the patch I mentioned above, updated my Primary Data Sources, and the issues were resolved.

Cheers.

caves

Will wait for the next release to see if that resolves it.

DavidRE

I am having this same issue. It happens when there is no data (date) for the column. The fix did work to get the correct dates in "Last Response". However, if there is a ticket without a response it should be blank... and it is for about 15 seconds... and then the "Just Now" pops up, and then counts up from there on all tickets without a response.

KevinTheJedi

DavidRE

Thank you for the comment. After testing, testing, and more testing I figured out it's when you use the Relative Date and Time filter on the column. Anyways, I have a patch ready and it's added to the pull request.

@caves DavidRE

Y'all can apply both changes in the pull request and it should fix both of the issues.

Cheers.

caves

This update has corrected the issue. Thanks for your help.

« Previous Page