Working with Multiple Browser Tabs

[SamuelPlentz]

Thank you!

Almost everything works like intended. URLs open directly in Zammad as intended.

We use Zulip as our chat and there it can linkify a text like #10123 to an URL. However I cannot use the URL https://Zammad/#ticket/zoom/10123 because internally the URL https://Zammad/#ticket/zoom/125 is needed. I worked around that by using the URL https://Zammad/#search/number%3A10123. That is not exactly related to your addon package though.

See also:

Open detail page for ticket with ticket number via url

Feature Request: Open the detail page for a ticket with an url containing the ticket number (not the internal ticket id). Currently there is no way to open the ticket detail page via a url from a external system. The ticket urls are only containing the internal ticket id which is not the ticket number. There should be an endpoint like: https://abc.com/#ticket/external/<ticketnumber> after opening this in the browser the detail page of the ticket will be displayed, same as if I use the inte…

[Stubenhocker]

I’ve created a PR for that here, as I think it might be a useful addition in general.

Fixes #849 - Allow additional usage of Ticket Number in (Zoom) URL

[Martin-Bonn]

Just FYI: Installed it, works great. Thanks!

[richie_77]

@bur

We are getting a lot Ticket Changes per mail. It’s easier to copy the ticket# from the mail and search for it in zammad, than clicking on the “open in zammad” link that causes a “you already have an open session”.

The same problem is in Zammad itself. I’ve tested around with the chat, if you store the chat conversation as a ticket, then only a link to the chat is stored. If you click on the link inside this ticket, it opens in a new tab and the other tab gets disconnected.

[bitshift]

Hi. Currently installed it in our (also agent-only) production setup with Zammad 5.2.1. Works like charm (It is really useful to force one and only Browser Tab with one and only active Zammad when clicking on Ticket links in other applications). Thank you so much.

We really tried to break the package’s expected behavior … but it simply worked reliably so far :-D. Hope that gets into the core (at least as option). Will test with Common Users (and not only agents) in a lab instance soon.

Edit: Typos

[fthommen]

Works just fine @Stubenhocker . Thanks a lot to have found this solution to one of the few real nuisances of Zammad. And even w/o any deep changes to Zammad

[PepsiMan]

How do I install it on Windows?

[MrGeneration]

Zammad doesn’t support windows as server runtime environment.
As this is a technical question of whatever direction, please use your own thread for that.

[Rikuhak]

Just created an account just to say THANK YOU!

[colesnicov]

Hello @Stubenhocker,

after upgrading to Zammad 5.3 your plugin isn’t working anymore

[Stubenhocker]

I’ll check it out!

I’m slowly beginning to realize my mistake of posting about my addon in this thread directly rather than making a new post and linking to it, I didn’t intend to hijack the conversation ongoing here. Sorry!

For future discussions regarding the addon it’s probably best to just have it’s dedicated thread now here:

One Tab Only Addon

Hello! Coming from Working with Multiple Browser Tabs - #31 by colesnicov, to reduce the offtopic conversation from going there, I’m going to create a new post for the “one tab only” addon here again: This addon is a change I’ve added to our instance of Zammad. It is a javascript snippet which ensures only one tab is of Zammad is ever open at a time. It solves directly opening links from other chat platforms. It does so by sending out a window message with the current url to any other…

@colesnicov Please post details with what exact version of Zammad you’re using and if there are any errors reported in the console in the thread above or open a new issue in the addons github repo.

[AndreKR]

What’s the recommended workflow with Zammad when you get sent a link to a ticket by chat?

Frankly I find this “one tab only” idea bizarre, especially when trying to copy/paste from one ticket on one screen to another ticket on another screen.

[YetAnotherGerrit]

Hi Andre, I never copy&paste the link to a ticket to my colleagues. I instead copy&paste the ticket hook to them. Or some of my colleagues go fancy and use the shift+ctrl+2xdot shortcut to copy the ticket information into the clipboard. This will have the ticket id and the ticket title in it. I just drop the ticket id into my search, instead of pasting the link to my browser.

See Keyboard Shortcuts — Zammad (for Agents) documentation for more information on that shortcut.

[AndreKR]

I don’t quite follow. Who are you quoting?

[MrGeneration]

I’ve removed that post due to off topic and unclear quotation.
Please use own threads if you have technical questions.

It doesn’t help the matter of this thread nor speeds it up at all.

[Hardy]

Hello,

as a user, I have a large problem with Zammad not being able to be open in two windows with the risk of losing content typed, but not saved.

It is a pretty common scenario that you write a KB article, and have a ticket open at the same time, where you copy things from, or even work in as well.

It is highly annoying that content is lost when not saved. And for me as a user it is of not interest why this is so. Zammad is the only application I ever had in my fingers where such a copy and paste is so extremely risky.

So, please, find a practicable way to allow this pretty normal workflows.

[dominikklein]

The new Desktop-UI will allow multiple browser tabs.

But for now switchting between a ticket and the current knowledge base article should also not be a real problem.

When you write a knowledge base article, and you switch via the Zammad taskbar to an open ticket and copy something, then you can click again on the knowledge base navigation entry, and you should be back to the last open knowledge base article without any data loss (important is no browser reloads during these steps, which are normally not needed).