# Ticket Lock missing

**URL:** https://community.zammad.org/t/ticket-lock-missing/38
**Category:** Completed Features
**Created:** [November 16, 2017, 9:32am UTC](https://community.zammad.org/t/ticket-lock-missing/38 "2017-11-16T09:32:40Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Hannes](https://community.zammad.org/user_avatar/community.zammad.org/hannes/32/3_2.png) [@Hannes](https://community.zammad.org/u/Hannes)
#### Post date: [November 16, 2017, 9:32am UTC](https://community.zammad.org/t/ticket-lock-missing/38/1 "2017-11-16T09:32:40Z")

</div>

> When you get a new notification for a new ticket. More than one agents can answer the same time with no notice of each other.

> petervanbeugen commented on Jan 22  
> I agree that the possibility to lock tickets (system wide on/off/auto setting?) is essential. In higher ticket /agent volume environments this becomes a nightmare. I’m a heavy OTRS user and have a (Znuny developed) package to be able to auto-lock a ticket as soon as it is opened by an agent. This would be nice in Zammad as well… A temporary workaround in Zammad could be to add a field in the Overwiews where you can see if a ticket is in use by an agent.  
> I like the idea and cane imagine use cases to work with more than one agent on a ticket, but then it should be possible to invite another agent to the ticket.

Imported:

> <https://github.com/zammad/zammad/issues/246>
>
> When you get a new notification for a new ticket. More than one agents can answe…r the same time with no notice of each other.

---

<div class="post-metadata">

### Author: ![Hannes](https://community.zammad.org/user_avatar/community.zammad.org/hannes/32/3_2.png) [@Hannes](https://community.zammad.org/u/Hannes)
#### Post date: [January 16, 2018, 5:32am UTC](https://community.zammad.org/t/ticket-lock-missing/38/2 "2018-01-16T05:32:48Z")

</div>

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