Skip to content

Issues: CodeTanzania/open311-api

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.

Sign up for GitHub

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

29 Open 2 Closed
29 Open 2 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Should have average attend time and average resolve time breakdowns per workspaces workspaces enhancement
#35 opened Feb 20, 2018 by BenMaruchu
@lykmapipo @BenMaruchu
In report response should have breakdown of service requests per statuses based on their reporting methods enhancement
#34 opened Feb 20, 2018 by BenMaruchu
@lykmapipo @BenMaruchu
In report response the workspaces should have breakdown of service requests based on their status enhancement
#33 opened Feb 20, 2018 by BenMaruchu
@lykmapipo @BenMaruchu
Update API documentation to accommodate latest changes documentation
#32 opened Dec 18, 2017 by BenMaruchu
Should provide/expose data frames API endpoint to allow for statistical analysis tools to utilize the data further enhancement
#31 opened Dec 18, 2017 by lykmapipo
Implementing the cache layer when applicable enhancement
#30 opened Dec 18, 2017 by lykmapipo
Finalize full implementation of OAuth v2.0 to force API client to utilize the standard feature
#29 opened Dec 18, 2017 by lykmapipo
Send a notification(Email and SMS) to customer care operator when service request is resolved enhancement
#28 opened Dec 18, 2017 by lykmapipo
Send a notification(Email and SMS) to jurisdiction when new service request submitted enhancement
#27 opened Dec 18, 2017 by lykmapipo
Based in service SLA notify correspondent when service request is past the allowed resolve time feature
#26 opened Dec 18, 2017 by lykmapipo
When service requested assigned send a notification(SMS and Email) to assignee with the details and ticket number of the service request. enhancement
#25 opened Dec 18, 2017 by lykmapipo
When service request closed(resolved) send notification(sms, email or push) to a reporter enhancement
#24 opened Dec 18, 2017 by lykmapipo
Create Production Deployment Documentation documentation
#23 opened Dec 18, 2017 by lykmapipo
When service request is closed(i.e status changes to closed) by assignee(or agency) notify original jurisdiction operator who opens the system or any other operator so that they can provide feedback to a customer(or civilian) feature
#22 opened Dec 18, 2017 by lykmapipo
Add default correspondent(agency) to be notified in case of emergency base on specific service or service group(category). Correspondent may be per jurisdiction or overall feature
#21 opened Dec 18, 2017 by lykmapipo
Notify jurisdiction operators when issue received from other end points(channels) i.e android, ussd etc. feature
#20 opened Dec 18, 2017 by lykmapipo
Add productivity reports that show how jurisdictions, operators, technician, engineers are performing based on issue reported, progress and resolving. feature
#19 opened Dec 18, 2017 by lykmapipo
Add performance reports based on established metrics such as SLA etc so as to provide an insights on how jurisdictions are close or far from their targets feature
#18 opened Dec 18, 2017 by lykmapipo
Add trending reports that will show how submitted service requests vary with time based on their services etc. feature
#17 opened Dec 18, 2017 by lykmapipo
Should support .env file to load environment variables. feature
#16 opened Dec 18, 2017 by lykmapipo
Create Heroku Deploy Button to allow user to deploy sample to heroku than using existing one feature
#15 opened Dec 18, 2017 by lykmapipo
Should add pagination for get permissions request enhancement
#13 opened Aug 12, 2017 by BenMaruchu
@lykmapipo
Should fix all the routes which are not found and make sure they are accessible
#12 opened Aug 12, 2017 by BenMaruchu
@lykmapipo
Return error JSON response for not allowed methods enhancement
#11 opened Aug 12, 2017 by BenMaruchu
@lykmapipo
Ensure all endpoints are documented documentation
#7 opened Aug 5, 2017 by lykmapipo
@BenMaruchu
ProTip! Follow long discussions with comments:>50.