Allow Organisation Updates on Closed Tickets via “Modify Tickets” | The place for Zendesk users to come together and share
Skip to main content
Feedback submitted

Allow Organisation Updates on Closed Tickets via “Modify Tickets”

Related products:Support
  • February 12, 2026
  • 2 replies
  • 0 views

Amie11

 

Request:

 

Please allow ticket Organisation to be updated on closed tickets using the Modify Closed Tickets functionality.

 

Why This Matters:

 

In real-world support environments, there are scenarios where tickets are:

  • Closed before the correct organisation was aligned
  • Migrated from another system with missing or incorrect org data
  • Created by end users not properly linked to their organisation
  • Impacted by org restructures, mergers, or reassignments

Currently, once a ticket is closed, we cannot realign it to the correct organisation via bulk update. This creates reporting inconsistencies and historical data integrity issues.

 

Reporting Impact:

 

Organisation alignment affects:

  • Explore reporting accuracy
  • Customer account health tracking
  • Contract/SLA reporting
  • Revenue or account-based analytics
  • Enterprise customer segmentation

 

If historical tickets remain linked to the wrong org (or no org), reporting becomes fragmented and unreliable.

 

Proposed Enhancement

 

Allow the Organisation field to be editable on closed tickets via:

  • Modify Tickets closed tickets - Within the Zendesk UI
  • Via API (if not already supported)

To preserve data integrity, this could be:

  • Restricted to admins
  • Logged in ticket events/audit logs
  • Optional via an admin toggle

This would significantly improve historical data hygiene and reporting reliability for enterprise environments.

 

Thanks for considering this enhancement — happy to provide example scenarios if helpful.

2 replies

Emily31
  • Product Manager
  • February 13, 2026
HI Amie! Thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review. For others who may be interested in this feature request, please add your support by upvoting this post and/or adding your use case to the comments below. Thank you again!
 

Scott12
  • February 16, 2026

+1 As an admin, I would love the ability to be able to set certain fields or relationships as “required” or “requested”. If a field is required the agent should not be able to close the ticket until it is completed (similar to forms current behaviour) and if it is requested then they should get a warning that requested fields have not been updated, the user should then have to provide a reason for why they have not been updated or, go back and update them.