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

Audit the priority levels for NewGtfsErrorType #272

Open
landonreed opened this issue Feb 4, 2020 · 0 comments
Open

Audit the priority levels for NewGtfsErrorType #272

landonreed opened this issue Feb 4, 2020 · 0 comments
Labels

Comments

@landonreed
Copy link
Contributor

Many of the NewGtfsErrorType priority levels appear to be mismatched with reality. Given recent work in Data Tools server to expose issue priority for display in the UI, these priority levels need an audit in order to verify their accuracy. Perhaps a set of criteria should be developed to help equate priority to a set of practical effects (e.g., high priority assigned if GTFS feed breaks during OTP build, medium priority if trip or other entity is dropped, low priority if no effect in third party app).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant