bcgov / bcgov/wps

Add columns to table for FBA

Open
#1,902 0 comments 0 reactions 0 assignees View on GitHub
4Refinement User Story
Dominant language
Python
Stars
65
Forks
11
Avg merge
21h 25m
Merged PRs (30d)
70

Description

As a FBAN/FBS I want to see a summary of fire behaviour indices and calculations So That I can quickly scan the context (e.g. severity) for stations crossing thresholds, and so that the required information per OSWS 5 is automatically generated

**Acceptance Criteria**
- [ ] Given I am using FireBAT, When I view the table, Then I see the following columns with headings:
- Zone (just the code)
- Weather Station
- Fuel Type
- Grass Cure
- Wind Speed
- HFI
- Critical Hours 4,000 Kw/m
- Critical Hours 10,000 Kw/m
- ROS
- 30 min Fire Size
- 60 min Fire Size
- Fire Type
- [ ] Fix sorting by zone - in Coastal FC, zone order appears as V1 > V10 > V2... Should be V1 > V2 > ... > V10.

**Definition of Done**
- [ ] Ready to Demo in Sprint Review
- [ ] Does what I have made have appropriate test coverage?
- [ ] Documentation and/or scientific documentation exists and can be found
- [ ] Peer Reviewed by 2 people on the team
- [ ] Manual testing of all PRs in Dev and Prod
- [ ] Merged

Contributor guide

Open the contributing guide

Research direction

Start at the FireBAT table entry point and trace how station rows, fire-behaviour values, and zone labels are assembled. Check the existing table tests, if present, before adding coverage for every requested heading and natural zone ordering. Done means the columns and sorting match the acceptance criteria and the result is ready for the stated review and testing process.

Written by the indexing model from the issue text.

Assessment

Tech stack
react
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.