Gaurav Parbat

Hey there, thank you for taking the time to provide us with this feedback! 
 
This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. 
 
 
Thank you again for your feedback and for being a valuable customer with Zendesk.
 

Hi all, 

I understand this is a gap and I have added it to the backlog for future consideration. We will consolidate this with field level permissions on tickets. This also means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. 

Hi all, 

Unfortunately this item is not on our near term roadmap. We wanted to let you know that at this time we are not able to commit to building this feature. We will review this request in 2026. We understand this may be frustrating but wanted to ensure we closed this loop to remain transparent. At this time we are going to close this post for comment and mark it as “not planned”. If you are interested in learning more about this and other features being built please make sure to check out and follow our Community events, What’s New Community Topic, and Zendesk Updates. Again, we apologize for our delay and appreciate you being a valuable Zendesk Community member.

Hi all, 

This is a great feature request and I have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community.

Hi all, 

This is a very specific condition and currently not on our roadmap. We understand this may be frustrating but wanted to ensure we closed this loop to remain transparent. At this time we are going to close this post for comment and mark it as “not planned”. If you are interested in learning more about this and other features being built please make sure to check out and follow our Community events, What’s New Community Topic, and Zendesk Updates. Again, we apologize for our delay and appreciate you being a valuable Zendesk Community member.

Hey all, 

We are working on making more improvements to the trigger condition builder and will consider this enhancement for our 2025 planning. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. 

Hi All, 

This capability is available in an EAP program built on top of our AI add on. You can find more details here. 
https://support.zendesk.com/hc/en-us/articles/6885971957914-Merging-related-tickets-based-on-AI-suggestions-EAP
 

Hey all, 

I have added it to the backlog for future consideration. Specifically the ability to move or minimize tag fields.  Field level permissions will be a key area of investment in 2025.  We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community.