Skip to main content
Answer

Ticket Status for Workspace Only

  • April 3, 2024
  • 3 replies
  • 59 views
volcanicdove
Skilled Expert
Forum|alt.badge.img+5

Is it possible to add a ticket status for only a specific workspace? I am attempting to modify the ticket status field inside of a Workspace, but it is inheriting from the Global ticket fields and shows that it is unable to be edited. The documentation mentions the ability to modify the ticket status field inside of a workspace, but in practice this doesn’t appear to be possible.

Understanding Custom Ticket Statuses: https://support.freshservice.com/en/support/solutions/articles/155560--understanding-custom-ticket-statuses

 

Best answer by volcanicdove

Workaround is using a Business rule. 

 

Yep, thanks for the reply, I have that implemented now. The status is in the global scope, and restricted by a business rule for each workspace. It’s inconvenient to maintain these over many workspaces, but if that’s what we have to do I guess I can deal with it for now.

 

Another workaround is making a new field with some type of status subtype, depending on your use case.

 

With that said, the answer to this question appears to be a simple “No.”

3 replies

Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

Is it possible to add a ticket status for only a specific workspace? I am attempting to modify the ticket status field inside of a Workspace, but it is inheriting from the Global ticket fields and shows that it is unable to be edited. The documentation mentions the ability to modify the ticket status field inside of a workspace, but in practice this doesn’t appear to be possible.

Understanding Custom Ticket Statuses: https://support.freshservice.com/en/support/solutions/articles/155560--understanding-custom-ticket-statuses

 

Workaround is using a Business rule. 

Synerity | Your Nordic Freshworks Partner | Seamless Support & Solutions | www.synerity.eu
volcanicdove
volcanicdove
Skilled Expert
Forum|alt.badge.img+5
  • volcanicdove
  • Author
  • Skilled Expert
  • Answer
  • April 4, 2024

Workaround is using a Business rule. 

 

Yep, thanks for the reply, I have that implemented now. The status is in the global scope, and restricted by a business rule for each workspace. It’s inconvenient to maintain these over many workspaces, but if that’s what we have to do I guess I can deal with it for now.

 

Another workaround is making a new field with some type of status subtype, depending on your use case.

 

With that said, the answer to this question appears to be a simple “No.”

Daniel Söderlund
Kamakshi V
Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

True I can’t see any other option. 

Synerity | Your Nordic Freshworks Partner | Seamless Support & Solutions | www.synerity.eu
Kamakshi V
Terms of UseAccessibility statement