Content - Number Application Questions
- Dominant language
- TypeScript
- Stars
- 29
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
**User Story**
As a _ministry user_ I want to have the application questions numbered to quickly identify individual questions when communicating with students.
**Current Behaviour**
Questions are not numbered at all.
**Expected Behaviour**
Application questions are numbered so ministry staff can communicate clearly about specific questions/answers.
---
**Possible numbering options**
- start to finish numbers (1,2,3,4,5,etc) with sub-questions being alphabetically labelled (1A, 1B, 1C, 2A, 2B, etc) / master question list to determine numbers and not reorder based on omitted questions
- use a larger numbering system so it's less confusing when some question numbers are omitted (for example between FT/PT or the section for parents / partners) 01XXX (program: 01010, 01020, 01021, 01022, 01030 / personal: 02010, 02020)
- ??
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not identify any files, tests, or entry points. First resolve which numbering scheme should be used and how omitted questions and sub-questions are handled; done means application questions consistently display the agreed identifiers for ministry users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100