-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Allow for "link to service request" in URL #959
Comments
Suggestion: add sr link to popup? |
@adamkendis has feasibility been evaluated? |
@danarchen No design work is needed for this ticket. I've removed the UI/UX label. |
@adamkendis, Was thinking about this a bit. It might be good to create the shareable links like this: This would then pull up/redirect to the map with that request in the popup. My thinking is:
Any thoughts? |
I'll build this as laid out in your initial comment - going to 311-data.org/srnumber/1-1234567 will load the dot for that service request on the map and open the popup. |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in X days. |
@adamkendis if this work hasn't been started yet, is there any objection to moving this issue into v3 scope? |
Task item:
Notes: |
After testing, the service request link does not render the desired service request page. UX: What is the use case for this feature?
Review with Engineering Resource |
Closing this issue after team discussion for lack of feasibility. |
Description
Basically, it would be great to have a permanent link to a service request. Some URL that had the sr number in the query string for instance. This would let people bookmark service requests, email them, etc. We could also link to them from reports!
Action Items
Build something in the client that would parse the SR number out of the query string and show it on the map. Would just center to the request with the popup displayed. Would likely need to work for any SR (even ones that were closed, etc.)
The text was updated successfully, but these errors were encountered: