Attempting to post the service request can fail without a response from uReport. The only error messaging supported in code is always expecting response.

We need to have an additional error check for errors with no uReport response received. Things like network errors or uReport being down altogether.

Undefined array key "code"
ServiceRequestController
line 34

Cliff, is there a demo of this client? regards from Patagonia

There are now cases where the same form post is coming in multiple times in less than a second. The timestamp on the tickets are the same, meaning the browser sent the form post really quickly back to back.

The current static image hosting is expecting us to create a separate directory for each deployment. For now, all development deployments are pointing against the same uReport server, so the groups are going to be the same.

Ultimately, the group images should probably be hosted by the uReport server we point to. This needs a new feature added to uReport so we can declare images for each Service and Group.

In the meantime, just move all the images up into the base /ureport-client directory on our static server.

City-of-Bloomington/uReport#405

The current way we select the group and service to report leaves out the descriptions of the services. It would be best to provide all the names and descriptions of the services. Also, we want to make sure it is as accessible as possible.

Marking up the service choosing as a single screen with details and summary would likely be the best case for accessiblity.

There are too many categories for citizens to dig through and find what they want to report about. THe previous javascript client provided a search box that searched through category names and descriptions.

We should provide a search box in this new client as well.

This client provides a way to look up a service request by ticket_id. When the ticket_id does not exist in uReport, the page errors out. The client should display some form of 404 when this happens.

When the site opens in mobile screen sizes, the logo changes to just the snowflake. We want to still display Bloomington, even on small screens.

The best idea is to add the city name as text to the header and change the logo to always use the small logo, instead of the logo with text.

The ansible playbook is still the generic skeleton ansible playbook from Blossom. This needs to be updated for a real deployment; so, when we go live, we can deploy with Ansible.

To simplify development, we are adopting Bootstrap as the core markup. This means we do not have to maintain two sets of templates, one for core and one for the bootstrap theme.

On the screen when choosing a Group and Service, the groups do not provide any descriptions. We want to have a curated description for each group. This will likely be a list of services in the group, but could be any text we want.

Because there is no information in uReport for the groups, we'll need to inject the custom text, somehow, from the config.

Currently, when typing in an address, the Google locator is looking for any address in the world that matches what you type. The Google API has filtering parameters we should use to limit the lookup to only our city.