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.

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

Performance: Improved touching assets of users, organizations and tickets #2911

Closed
rolfschmidt opened this issue Jan 28, 2020 · 0 comments
Closed

Comments

@rolfschmidt
Copy link
Collaborator

@rolfschmidt rolfschmidt commented Jan 28, 2020

Infos:

  • Used Zammad version: 3.2
  • Installation method (source, package, ..): all
  • Operating system: all
  • Database + version: all
  • Elasticsearch version: all
  • Browser + version: all

Frontend improvements

  • The organization profile did not update the member list of the organization if the member list has changed.
  • The user avatar images in the organization profile was not updated correctly if the user has changed his avatar.
  • The user avatar images in the user profile was not updated correctly if the user has changed his avatar.
  • The organization name in the user profile was not updated correctly if the user has changed his organization.
  • The organization members in the ticket detail view were not updated correctly if the user has joined or left a organization.
  • The user avatar images in the ticket detail view were not updated correctly if the user has changed his avatar.

Backend improvements

  • The frontend got blocked by massive database requests because of the association update of organization. If you update a organization with many users or tickets then the acting user has to wait a long time. All associations changes are now async.

  • For associated objects (except ticket) the elastic search update was always updating the hole attributes of the object instead of only updating the referenced attribute data.

  • The build_url function of search_index_backend.rb was not very readable and got refactored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.