# TicketID is not the URL ID

**URL:** https://community.zammad.org/t/ticketid-is-not-the-url-id/8490
**Category:** Technical assistance
**Created:** [January 20, 2022, 1:09pm UTC](https://community.zammad.org/t/ticketid-is-not-the-url-id/8490 "2022-01-20T13:09:15Z")
**Posts on this page:** 7
**Page:** 2

<div class="post-metadata">

### Author: ![nova](https://community.zammad.org/letter_avatar_proxy/v4/letter/n/c5a1d2/32.png) [@nova](https://community.zammad.org/u/nova)
#### Post date: [May 10, 2022, 10:38am UTC](https://community.zammad.org/t/ticketid-is-not-the-url-id/8490/21 "2022-05-10T10:38:21Z")

</div>

> [@MrGeneration](#):
>
> Mate, look at ANY productive ticket within your instance and have a lurk into the address bar of your browser.

I know, but this is the internal ticket id, not known to our external system. So we need open the detail page via a url with the public ticket id. This brings up the origin problem.

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [May 10, 2022, 10:39am UTC](https://community.zammad.org/t/ticketid-is-not-the-url-id/8490/22 "2022-05-10T10:39:12Z")

</div>

There is no such thing like “internal” and “external” ticket id.  
You may want to stop to mix terminologies.  
I’m stopping at this point.

---

<div class="post-metadata">

### Author: ![richie\_77](https://community.zammad.org/user_avatar/community.zammad.org/richie_77/32/5964_2.png) [@richie\_77](https://community.zammad.org/u/richie_77)
#### Post date: [May 11, 2022, 7:59am UTC](https://community.zammad.org/t/ticketid-is-not-the-url-id/8490/23 "2022-05-11T07:59:55Z")

</div>

> [@awedor](#):
>
> When we implemented Zammad in our company the ticket ID and the ticket number were identical so the users got used to being able to just enter the number (without prefix) in the url to open a specific ticket for example when you are on the phone with a colleague and he / she says “could you have a look at ticket 123…” we just put the number in the url and have the ticket open.

Why you don’t use the search box to search for the ticket number?

> [@awedor](#):
>
> Technically it would be no problem to ensure the number and the id always match when creating a new ticket so maybe you are correct that this is not a bug, but it definitely would be an enhancement to the usability of Zammad that would reduce questions and discussions about this in the future.

When you ensure, that the numbers always match, then for what do you need two numbers?

---

<div class="post-metadata">

### Author: ![richie\_77](https://community.zammad.org/user_avatar/community.zammad.org/richie_77/32/5964_2.png) [@richie\_77](https://community.zammad.org/u/richie_77)
#### Post date: [May 11, 2022, 8:00am UTC](https://community.zammad.org/t/ticketid-is-not-the-url-id/8490/24 "2022-05-11T08:00:45Z")

</div>

> [@nova](#):
>
> This helps a little bit, but the problem is that the user still has to select the ticket in the result list to see the details of the ticket. Its a additional step which every ticket agent has to do to get the details of the ticket. As we have many tickets to be opened from our external system this is not very practical for our users.

Make an API-Request, that searches for the ticket with the given ticket number, get the ticket id from the request result and then call the URL with the ticket id from the result to get the detail view of the ticket. I’m sure, this can be done in an external application.

---

<div class="post-metadata">

### Author: ![marcungeschikts](https://community.zammad.org/user_avatar/community.zammad.org/marcungeschikts/32/5331_2.png) [@marcungeschikts](https://community.zammad.org/u/marcungeschikts)
#### Post date: [May 16, 2022, 7:09am UTC](https://community.zammad.org/t/ticketid-is-not-the-url-id/8490/25 "2022-05-16T07:09:27Z")

</div>

OK then I can understand your point that urlid has not link with ticketid (which is not user friendly and not the case for tools like github, gitlab,… btw)

But then the bug is that: when I do a search for example 6389 , Zammad will not find ticket 776389, but the ticket with url id 6389…at least Zammad should find both.

---

<div class="post-metadata">

### Author: ![MrGeneration](https://community.zammad.org/user_avatar/community.zammad.org/mrgeneration/32/9260_2.png) [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [June 17, 2022, 12:57pm UTC](https://community.zammad.org/t/ticketid-is-not-the-url-id/8490/26 "2022-06-17T12:57:35Z")

</div>

> [@marcungeschikts](#):
>
> But then the bug is that: when I do a search for example 6389 , Zammad will not find ticket 776389, but the ticket with url id 6389…at least Zammad should find both.

Just wildly guessing, you’re hitting known search hard limits (10 or 50 depending on the UI part).  
It does work, you can find the ticket by it’s id and number

![image](https://community.zammad.org/uploads/default/original/2X/7/76c96af31c12375eb28b50a1a56cbb48dc2aca6e.png)

You can also run specific searches for specific attributes:  
[https://user-docs.zammad.org/en/latest/advanced/search.html](https://user-docs.zammad.org/en/latest/advanced/search.html)

---

<div class="post-metadata">

### Author: ![system](https://community.zammad.org/uploads/default/original/1X/5c5afaea2d23f811dbec33cd4edb02fa29d3262f.png) [@system](https://community.zammad.org/u/system)
#### Post date: [October 15, 2022, 12:58pm UTC](https://community.zammad.org/t/ticketid-is-not-the-url-id/8490/27 "2022-10-15T12:58:30Z")

</div>

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.

[Previous page](https://community.zammad.org/t/ticketid-is-not-the-url-id/8490.md?page=1)
