View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001584 | Garmin Badge Database | Task | public | 2023-11-06 16:00 | 2023-12-21 15:42 |
| Reporter | e7andy | Assigned To | e7andy | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Target Version | 2023 | Fixed in Version | 2023 | ||
| Summary | 0001584: Calculate finish date for expeditions | ||||
| Description | Calculate finish date for expeditions. Use the userJoined flag to see what expeditions/challenges the user has joined. I can probably change the function "fetchBadgesFromGarmin" in the extension to only use the badgechallenge-service to get the data. Return the uuids that should be fetched. Create new methods to not stop the old code for users that haven't updated yet. The expedition/Challenge Id is the same as BadgeUuid (uuid in the DB). Ex. Denali got uuid: E40D57A63B7C49C7B39B725A0189949B Get joinDateLocal: https://connect.garmin.com/badgechallenge-service/badgeChallenge/E40D57A63B7C49C7B39B725A0189949B | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-11-06 16:00 | e7andy | New Issue | |
| 2023-11-06 16:00 | e7andy | Status | new => assigned |
| 2023-11-06 16:00 | e7andy | Assigned To | => e7andy |
| 2023-12-21 15:42 | e7andy | Status | assigned => resolved |
| 2023-12-21 15:42 | e7andy | Resolution | open => fixed |
| 2023-12-21 15:42 | e7andy | Fixed in Version | => 2023 |
