Hmm, I think we can add that. We already show the category name. Likely it'll be shown for support users only. I don't see why users need to see Tender categories or IDs personally.

Often when we invoice our clients, they want to be able to refer to
the ticket that they're being invoiced for, so we need some sort of
universal reference for each ticket.

Thanks

This discussion was assigned to ticket 495.

I'd really like this too - every other support system I've seen lets you put the ticket number in the email subject, I was surprised Tender couldn't do this.

Some of our larger customers have 30-40 issues open at a time, so the ticket number is the only way to reliably keep track of particular issues.

Update!

No development is needed thanks to Liquid. Here is an example subject line for an auto responder: (word wrapped)

Versatilia has received your request
   [ticket {{ url | remove:'http://support.versatilia.com/discussions/' | 
           remove 'problems/' | remove 'suggestions/' | remove 'questions/' |
           replace:'-',' ' | truncatewords:1 | remove:'...' }}]

renders as:

Versatilia has received your request [ticket 37]

To use it just replace the URL with your own, and if you have any customised categories, include/change those too.

Sorry one more update - last one I promise!

I just realised the ticket numbers are unique to each category, so here's an alternative:

   [{{ url | remove:'http://support.versatilia.com/discussions/' |
     replace:'/',' ' | replace:'-',' ' | truncatewords:2 | remove:'...' }}]

renders with the category name, like this:

[questions 3]
[problems 17]
etc...

Yes, the development is easy. QA, documentation, and support isn't
quite as easy. It's on the list though, probably after our next big
features (Filters and Reporting).

More feedback on this feature request:

1. Ticket Numbers need to be global to the entire tender account, not category specific. From the organizations perspective, when passing or referencing tickets, categories are subject to change, but ticket numbers need to be canonical.

2. Account should have option of displaying numbers on ticket list and detail pages. See FogBugz for how they use case #s - they are a primary way of navigating to cases quickly.

3. Searching for a ticket id, should take you directly to the ticket, not return results then requiring an additional click to get to the detail