Closed AngelaKabari closed 5 months ago
Let's look into options without a product change before we work on this.
@pld the other option is: To have textboxes shown or hidden using skip logic, depending on which answer options the user picks.
E.g. if "Taking pills" was selected, then show a textbox below the whole checkboxes, as a separate Questionnaire Item (not directly below that selected checkbox, which is what the ticket trying to do).
Ah right I see, what we split these up into a different question for each option? Then we could have a different hidden text box show per question directly below it
@pld yeah I'm fine w that.
~@AngelaKabari could you try to convince the client about this?~ EDIT: NVM this shouldn't look that different compared to what the client want initially, the margins between options might be different a bit
I agree @FikriMilano - as long as the UI doesn't look very different then I don't think we would need to convince the client.
Describe the feature request. We have a questionnaire that has a question with several check box options. If an answer choice is checked, then we would like a free response text box to appear below the checkbox option so that the provider can capture further information about the choice that has been selected.
Additional context
In the screenshot above, if an answer choice is checked, a free response text box titled "Take detailed history" should show up under that choice (e.g., if “Taking pills” is checked, then a free text box emerges right under the choice) to allow the provider to capture details on the nature and quantity of the pills, how frequently, etc
Acceptance criteria
Area path A list of ordered steps in the app on usage of the feature to support anyone testing it e.g. Code reviewer, QA e.g.
Implementation plan (For Engineers) The plan for implementing the solution e.g. via a description or a check list for the various ordered tasks that will need to be completed. i.e. Describe how you intend to solve the problem