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

Add Request Source to API reports and service requests (?) #937

Closed
mattyweb opened this issue Feb 9, 2021 · 1 comment · Fixed by #978
Closed

Add Request Source to API reports and service requests (?) #937

mattyweb opened this issue Feb 9, 2021 · 1 comment · Fixed by #978
Assignees
Labels
Size: 8pt Can be done in 31-48 hours

Comments

@mattyweb
Copy link
Collaborator

mattyweb commented Feb 9, 2021

Currently, the request source is not available for reporting or on the service request detail page.

If we wanted to count the number of requests coming in from the mobile app vs the phone vs the web we'd need to include this.

NOTE: would like direction as to whether this would be used. Maybe the data team should first analyze whether source has an impact on time to close, etc.

@mattyweb mattyweb added the Size: 8pt Can be done in 31-48 hours label Feb 9, 2021
@mattyweb mattyweb self-assigned this Feb 9, 2021
@mattyweb mattyweb added this to the Initial v2 Launch milestone Feb 9, 2021
@mattyweb
Copy link
Collaborator Author

mattyweb commented Feb 9, 2021

This would need to be added to the view and to several endpoints. We'd likely also need an entity for this (and API endpoint).

@mattyweb mattyweb removed this from the Initial v2 Launch milestone Feb 9, 2021
mattyweb added a commit that referenced this issue Mar 1, 2021
Fixes #937
- can report by source_name dimension
- can filter by source_name
- added tests
@mattyweb mattyweb added this to the Initial v2 Launch milestone Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Size: 8pt Can be done in 31-48 hours
Projects
Development

Successfully merging a pull request may close this issue.

1 participant