Feature limitations for EAP | Community
Skip to main content

Feature limitations for EAP

  • September 16, 2022
  • 15 replies
  • 0 views

Colleen13

This early access program (EAP) currently has the following limitations. We plan to address these things before the General Availability (GA) release. Keep an eye on this article to keep up to date with any changes.

  • Deleting ticket statuses: You cannot delete a ticket status.
  • Conditional ticket fields: Ticket statuses that you create can’t be used in conditional ticket fields. 
  • Support placeholders: Ticket statuses that you create can’t be used in placeholders. The existing {{ticket.status}} currently displays the status category.
  • Explore integrations: New ticket statuses are available for a subset of reporting metrics in Explore. See Custom ticket status attributes in Explore.
  • Contextual workspaces: Using new ticket statuses with Contextual Workspaces in not yet supported. If you use new ticket statuses in a contextual workspaces condition, then you can’t submit tickets within that workspace.
  • Jira integrations: New ticket statuses are not yet available for Jira integrations.
  • Keyboard shortcuts
  • ZAF

Known issues

This EAP currently has the following known issues:

  • The new My Requests page in Guide only displays status category and doesn’t show new ticket statuses.
  • The Suspended Ticket view doesn’t display the Ticket status column correctly and misaligns other columns.
  • When you disable ticket statuses from the Settings page, you must refresh the page to access the “Activate ticket statuses” button within the Ticket Statuses menu.
  •  It’s possible to add a second status with the same label as a default status from another status category. For example, it’s possible to add a status labeled “Open” under the “Pending” category, resulting in having two statuses with the same label, “Open - Open” and “Pending - Open”.

15 replies

Charis11
  • October 18, 2022

Hello,

 

Is there a target date for when custom ticket statuses will be available for reporting in Explore? I am having a hard time capturing mean time to recovery without this functionality. Would appreciate some guidance on what I can do in the interim.

 

Thank you,

Charis


Yoram11
  • October 22, 2022

Hi,

 

Will the statuses be added as exit conditions in the automation?

Currently, you cannot use them as exit conditions.

 

Thanks

Yoram


Dan12
  • November 9, 2022

@colleen13 Any updates on when we'll be able to report on statuses in Explore? That's the major thing holding back adoption for us.

@gaurav12 Last update I saw was that deleting statuses was expected at end of September. Has that shipped yet or was it delayed?


Aaron11
  • November 9, 2022

Any ETA on being able to use Custom Statuses in filters? 

I am currently using a custom status to indicate when an incident is pending development. These incidents can take many, many months to solve, but our customers want visibility. 

I filter these tickets out of our daily views, but they are included in all of our backlog and open ticket reports, which has been causing these numbers to gradually grow since we adopted the new feature. This is making accurate backlog reporting difficult. 

Thanks!


Colleen13
  • Author
  • November 9, 2022

Hi @dan12,

Thank you for your question! I learned earlier today that custom ticket statuses and ticket status categories are now available as ticket attributes in Explore. I'll be updating the documentation for that in this EAP community soon. 


Aaron11
  • November 9, 2022

This is exciting news!

I just tried it and confirmed this works for the Tickets data set, however, it does not appear to be available for the Backlog data sets. 

Thanks!


Colleen13
  • Author
  • November 9, 2022

Hi @aaron11,

I'm glad to hear that worked for you! I believe that Gaurav will be able to provide more information about availability for Backlog data sets.

Also, to answer your question about custom ticket statuses in filters, do you mean filtering Views? If so, yes you can filter Views by custom ticket status now. We introduced additional Views filtering capabilities last week (though custom statuses are not listed because this feature is still an EAP). I'll also be updating the documentation for that in this EAP community soon. Thank you! 


Aaron11
  • November 10, 2022

Hi Colleen, 

I was specifically referring to filters in Explore reports, sorry, that wasn't clear. 

You then answered my question a few minutes later :-)

Once we have that functionality in Backlog Data sets, we are golden!


J.10
  • November 17, 2022

Greetings,

How can I access the custom status value via a placeholder?

Thanks,

Greg


Colleen13
  • Author
  • November 17, 2022

Hi @j.10,

Placeholders are not yet available for custom ticket statuses. I'm updating this post and the EAP community as we continue to make progress so please keep on eye on this space for news.

Thank you!

Colleen


Bobby11
  • November 30, 2022

Is it not available in automations??? Only status category shows up. 


Colleen13
  • Author
  • November 30, 2022

Hi @bobby11,

Custom ticket statuses are available in automations. If you had existing automations that used the Ticket: Status condition or action, they are converted to Ticket: Status category when you enable custom ticket statuses.

Ticket: ticket status and Ticket: Ticket Hours since [ticket status name] are conditions for custom ticket statuses that should appear in the menu when you are creating or editing an automation. Please see EAP docs: Using ticket statuses in business rules, SLAs, macros, and views for more information.


Bobby11
  • November 30, 2022

Hi @colleen13!!

You are right, sorry folks! 

It is a little confusing, i did not realize the automation list was split by custom and default - doh!


Colleen13
  • Author
  • November 30, 2022

That's ok and thank you for the feedback @bobby11! I'll clarify this in the documentation before this feature GAs!


Robert17
  • January 10, 2023

Hi,

Reading these limitations - one struck me:

Conditional ticket fields: Ticket statuses that you create can’t be used in conditional ticket fields. 

In the GA release of custom statuses, can we expect that we will be able to use custom statuses as conditions for filling in fields for Conditional Fields?