Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add reassign reason + rename insights #17720

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sean-brydon
Copy link
Member

What does this PR do?

Here we add reassign reason to response csv export and also to data-table.

We also rename tabs to be summary,booking. Booking (previously routing) will provide a more detailed break down specific to bookings and routing form responses. Where as summary is/will become a more top level breakdown of the organization.

CleanShot 2024-11-18 at 11 36 01

How should this be tested?

  1. Reassign a routing form response booking with reason
  2. Check table
  3. Export data to CSV
  4. Open CSV - profit

Checklist

  • I haven't read the contributing guide
  • My code doesn't follow the style guidelines of this project
  • I haven't commented my code, particularly in hard-to-understand areas
  • I haven't checked if my changes generate no new warnings

@graphite-app graphite-app bot requested a review from a team November 18, 2024 11:37
@dosubot dosubot bot added insights area: insights, analytics routing-forms area: routing forms, routing, forms ✨ feature New feature or request labels Nov 18, 2024
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved to /bookings > /routing

@keithwillcode keithwillcode added consumer core area: core, team members only labels Nov 18, 2024
@@ -238,6 +238,7 @@ class RoutingEventsInsights {
uid: true,
status: true,
createdAt: true,
reassignReason: true,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add reassign reason to table

Comment on lines +624 to +625
"Reassigned By": response.routedToBooking?.reassignBy?.name || "",
"Reassigned Reason": response.routedToBooking?.reassignReason || "",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Provide Reassign reason and who reassigned in routing form export

@@ -89,14 +89,14 @@ const navigation: NavigationItemType[] = [
isCurrent: ({ pathname: path, item }) => path?.startsWith(item.href) ?? false,
child: [
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rename tabs - see PR description for reasoning.

Copy link

graphite-app bot commented Nov 18, 2024

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (11/18/24)

1 reviewer was added to this PR based on Keith Williams's automation.

Copy link
Contributor

@joeauyeung joeauyeung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heads up I've reassigned these two bookings but the reason isn't showing up. In routing-events I'm seeing the data contain the routeToBooking object.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
consumer core area: core, team members only ✨ feature New feature or request insights area: insights, analytics routing-forms area: routing forms, routing, forms
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants