Skip to content

ASA: Convention to highlight advisory end times into the next day #4427

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

Open
2 tasks
nealmcloughlin opened this issue Apr 9, 2025 · 0 comments
Open
2 tasks
Labels
4Refinement this ticket is ready for refinement with the team UX-Design

Comments

@nealmcloughlin
Copy link
Collaborator

Describe the task
ASA produces start and end times for when advisory conditions are expected in each of the unique fuel types in a zone. The fuel associated associated with >= 75% of the advisory area are mentioned in an advisory bulletin which specifies the minimum start time, and maximum end time, for these fuel types. In some circumstances the end time can extend into the next day. When this occurs, many users see this as an error and do not recognize that it refers to the next day. We need a convention so that users understand when the end time for an advisory is extends beyond today and into tomorrow.

Acceptance Criteria

  • A convention for advisory end times that extend beyond the day the advisory is issued for.
  • The convention can be applied to both the advisory bulletin and the fuel type table.

SME/User Contact
(may want to use a persona to fill this in)

Additional context

  • An example of this issue can be viewed in ASA by selecting the forecast for September 6, 2024 in the C5- Chilcotin Zone. Note the end hours for the C-2 and S-2 fuel types are 03:00.
@nealmcloughlin nealmcloughlin added 4Refinement this ticket is ready for refinement with the team UX-Design labels Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4Refinement this ticket is ready for refinement with the team UX-Design
Projects
None yet
Development

No branches or pull requests

1 participant