ASA: Advisory report structure when looking at Actuals
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**Describe the task**
Recent updates to the Advisory Report text have focussed on forecast data. What should the text look like when Actuals are selected?
One example of a problem is when there is no advisory or warning, we still show the text `Issued on August 15, 2024 at 3:21 PM PDT for Aug 15.` for Actuals while also saying `No advisories or warnings issued for the selected fire zone unit.`
**Acceptance Criteria**
- [ ] first
- [ ] second
- [ ] third
**Additional context**
- Add any other context about the task here.
- Or here
Contributor guide
Research direction
The issue names no files, tests, or entry points; start by locating the Advisory Report implementation and the Actuals selection path. Clarify the intended Actuals wording and replace the placeholder acceptance criteria with observable outcomes, including whether the issued-on line appears when no advisories or warnings exist.
Written by the indexing model from the issue text.
Assessment
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100