Feature Requests

Unless you manually change the name, Saved Searches get generated with "New Search" as a name by default. So unless you're disciplined and organized you'll probably end up with a page full of "New Search" without a clue which one is which. If we could generate names with some kind of unique identifier it'd make admins lives easier as well as helping us troubleshoot on our end. Or maybe surface the steps on the admin page table?

Right now, this is out of scope for a Conversation Code, but a suggestion.

If there are a lot of doors in a cluster, it can be difficult to tap on them.

Issue: While creating branching script, it is easy to make mistakes. In a recent attempt to create a script I received an error message because I enabled branching in two separate questions while simultaneously marking that the section should continue to a specific section. This was an error where I should have disabled branching and utilized the "continue to specific section" feature only. After multiple-save attempts, I kept seeing an error message. There was no indication that progress was saved, nor was there information about what the error was. When I reloaded my page - a risky choice since reloading without saving in script building is a destructive action - my script showed duplicates of the questions with the errors. The script duplicated "GOTV Ask" enough to take my 12 section script to a 26 section script. These issues are related. Without rich error messages, it is difficult to find the problem. When the error message appears during saving, the problem area is duplicated, but this is only visible when the page is reloaded. Reloading without saving is a potentially destructive action, erasing user progress. Potential Solution(s): 1) Error messages should give the user more information about what the issue is and where to find the error. It should - if possible - also offer a fix. 2) Script building should save progress automatically or encourage saving the script before reloading to avoid destroying progress 3) Errors during saves should not duplicate the area of the script throwing the error.

Issue: After importing a list, the post-import status page doesn't clearly indicate where to click to continue loading more lists leading the user to select the side-bar and return to imports to continue the process. This is burdensome for people importing multiple lists back to back. The link to continue imports falls at the end of the a paragraph and is colored in the dark-blue of OpenField branding, making it difficult to distinguish from the black font color. The font size for all items on that page is the same, making it difficult to distinguish between that hyperlink and other parts of the webpage. Additionally, the bread crumbs at the top are the only area using a different color and it draws the users eye to that section instead of the hyperlink at the end. The only content using a different font style is the all-caps that shows the type of list import used. The user's eye is distracted by two other better-distinguished parts of the page and thus becomes exhausted by the time the user comes across hyperlink at the end of the paragraph. Additionally, the hyperlink sends the user to the status of uploads and doesn't allow the user to continue uploading directly. Potential Solution: Two buttons may be helpful - one to return to imports status page and one to continue importing - both in a large dark-blue or other-colored button at the top of the page. This would limit the number of clicks the user needs to make to reach the page they want to reach.

When uploading a list to OpenField, if the list name is longer than 80 characters, the user sees an error message asking them to reduce the number of characters and the list is not loaded. This error handling causes unnecessary friction in the list import process - especially for users trying to upload multiple lists in a short period of time. A graceful failure could be for the file name to be cut down to 80 characters quietly by the importer and for the new list name with cut characters to show in the list name in the preview. This handling would improve user experience by not stopping the user's import and not forcing the user to return to their list, rename the list, and attempt a new load.

A map where you could see where your canvassars are / and be able to see where they were when they knocked - to make sure they are where they said they would be.

To see all canvassers out based on time (decided in the calendar picker) turf number of knocks when turf was checked out other stats

For clairty