-
Notifications
You must be signed in to change notification settings - Fork 3
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
Which Nextcloud Version are you currently using: (see administration page)
Nextcloud Hub 9 (30.0.8)
Is your feature request related to a problem? Please describe.
The integration works well, but it still feels kinda detached as it opens Zammad Ticket links on a new tab/window. Loading it in an iframe inside Nextcloud would feel a lot more "native".
Describe the solution you'd like
Have a dedicated page and load it via an iframe (configurable via settings).
All the ticket links rendered should use the internal page url + zammad path for hash routing (see patch below).
Describe alternatives you've considered
I am currently using the External app and added a small patch for Zammad's hash routing (it is common in many SPAs).
The integration_zammad app doesn't use a universal url generator and I had trouble changing the ticket urls in all views (widget, search results, smart picker). This will take a bit of refactoring.
Perhaps the best solution would be to detect if the External app is enabled (since iframe based menus and hash routing are already there), and if it is add the Zammad connected server as an External site entry instead of the plain link to the menu.
Additional context
An iframe won't be loaded by default when Nextcloud and Zammad are hosted in different (sub)domains. I use nginx reverse proxy for Zammad with the following headers:
add_header X-Frame-Options "ALLOW-FROM my.nextcloud.domain";
add_header Content-Security-Policy "frame-ancestors my.nextcloud.domain";