search

department-of-veterans-affairs / va-mobile-app

"If VA were a company, it would have a flagship mobile app."
https://department-of-veterans-affairs.github.io/va-mobile-app/
12 stars 2 forks source link

Fix NoMethodError: undefined method `[]' for nil for legacy disability ratings #9157

Closed jperk51 closed 1 month ago

jperk51 commented 1 month ago

New issue alert: https://vagov.ddog-gov.com/apm/error-tracking?query=%40issue.age%3A%3C%3D172800000%20env%3Aeks-prod%20resource_name%3AMobile%2A&fromUser=false&issueId=5810b474-3fd4-11ef-b362-da7ad0900007&refresh_mode=paused&source=all&view=spans&from_ts=1720565210000&to_ts=1720738010000&live=false

timwright12 commented 1 month ago

@jperk51 is this a bug? If so can we use the bug label for tracking purposes?

jperk51 commented 1 month ago

@timwright12 should I also mark them with severity ratings?

timwright12 commented 1 month ago

yeah, check with @bischoffa about that. I'm not sure how they handle API bugs

bischoffa commented 1 month ago

Looks like for Q2 there hasn't been any bug tickets created by the API team for API. They have a tech debt / bug epic but a few have the bug label and those are originating from other teams who believe there are backend implications. Looks like its more used for improvements / tech debt and not bugs.

@StacyB2023 lets talk about how the best way to proceed. I am assuming API team has some version of bugs so lets see how we want to handle them.

StacyB2023 commented 1 month ago

@bischoffa Yes, that epic is mostly tech debt and a mix of bugs that may have originated from other teams. If we need to use a tag for "bugs" when created as in this example we can note that for Q3.

That is not something we have been actively doing since we manage our tech debt and bugs (and most testing) independently.

cc: @jperk51