Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix getOfflineIdentifiers to handle the case a ticket does not have a last_update time #339

Closed
syjer opened this issue Sep 16, 2017 · 1 comment
Closed

fix getOfflineIdentifiers to handle the case a ticket does not have a last_update time #339

syjer opened this issue Sep 16, 2017 · 1 comment
Assignees
@syjer
Milestone
1.12

Comments

@syjer
Copy link
Member

syjer commented Sep 16, 2017 •
edited

It's possible that a ticket does not have the field -> this will cause to be always loaded by the getOfflineIdentifiers call
@syjer syjer self-assigned this Sep 16, 2017
@syjer syjer changed the title update latest_ticket_update to always include a time fix getOfflineIdentifiers to handle the case a ticket does not have a last_update time Sep 16, 2017
@syjer
Copy link
Member Author

syjer commented Sep 16, 2017

the query TicketRepository.findAllAssignedByEventId can be changed.

syjer added a commit that referenced this issue Sep 16, 2017
@syjer
#339 always use a date in TicketRepository.findAllAssignedByEventId
a4dd2a2
@syjer syjer closed this as completed Sep 16, 2017
@syjer syjer added this to the 1.12 milestone Sep 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@syjer syjer

Labels
None yet
Projects
None yet
Milestone
1.12
Development

No branches or pull requests
1 participant
@syjer