nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira sync dropping time-to-resolution — anyone seen this?

esme_voss_d0530

Trying to get CES tracking right for renewals at risk. The defaults don't quite fit. What did you change?

Find more posts tagged with

Comments

ivy_mehta_840df

We hit this too. Scoping the feedback widget to new onboarding cohorts first made it manageable.

marcus_rourke_05039

Spent a week on this. The fix was tying segments to the account owner field.

mira_vance_20004

Honestly response routing didn't move time-to-resolution for us. Microsoft Teams did more.

theo_hale_eedb4

+1. The Segment step is where ours kept breaking.

liam_pace_3f4ef

Worth checking your response rate window. Ours was skewed until we narrowed it.

priya_akoto_8ac43

Same setup here. In our case it came down to the in-app survey being too broad.

tom_rourke_1d83a

Have you tried routing it through Zendesk? Fixed the time-to-resolution gap for us.