Skip to content
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

Element/component: multiple choice and radio buttons #564

Closed
1 task
karpix opened this issue Dec 12, 2018 · 4 comments
Closed
1 task

Element/component: multiple choice and radio buttons #564

karpix opened this issue Dec 12, 2018 · 4 comments
Labels
area/ui-editor Area: Related to the designer tool for assembling app UI in Altinn Studio. Epic Used by zenhub to identify the epics that group issues. kind/user-story Used for issues that describes functionality for our users. skip-releasenotes Issues that do not make sense to list in our release notes status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design.
Milestone

Comments

@karpix
Copy link

karpix commented Dec 12, 2018

Functional architect/designer: @-mention
Technical architect: @-mention

Description
Iteration 2 for radio buttons and multiple choice:

  • Show content of radio buttons and checkboxes in view mode (not only in edit mode)
  • What happens when each check box or radio button can be linked to a separate datamodel element
  • What happens when a long text is added to a radio button or a checkbox
  • Bug Missing validation on "enumeration" #544

In the user test done in april 2019 around half of the participants failed to set up a checkbox. We need to re-evaluate the design for editing a checkbox and how we can simplify the process.
The following problems need to be adressed:

  • Confusing and not logic to add a checkbox inside the created checkbox
  • Don't undertand what "Manual" and "Kodeliste" means
  • Text on checkbox is not added to the textfile – this is both a translation problem and an consistancy in interaction problem

Sketch (if relevant)
(Screenshot and link to Figma, make sure your sketch is public!)

Navigation from/to (if relevant)
This functionality is reached from...

Technical considerations
Input (beyond tasks) on how the user story should be solved can be put here.

Acceptance criterea

  • What is allowed/not allowed
  • Validations
  • Error messages and warnings
  • ...

Tasks

  • Example task
@karpix karpix added this to the MVP.2 milestone Dec 12, 2018
@lvbachmann lvbachmann added area/ui-editor Area: Related to the designer tool for assembling app UI in Altinn Studio. team-tamagotchi labels Feb 8, 2019
@gudrunvigerustfuru gudrunvigerustfuru added the kind/user-story Used for issues that describes functionality for our users. label Feb 13, 2019
@lvbachmann lvbachmann modified the milestones: MVP.2, MVP.2 (Kanban) Feb 22, 2019
@malmil malmil added status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design. and removed needs-specification labels Mar 13, 2019
@GGunnar
Copy link

GGunnar commented Mar 20, 2019

@karpix multiple choice and radio buttons are already in the solution, therefore closing this issue, if there is a need to work on this, please create a new issue as this one seems to be outdated.

@GGunnar GGunnar closed this as completed Mar 20, 2019
@GGunnar
Copy link

GGunnar commented Mar 20, 2019

Reopening this after discussion with helenekri

@GGunnar GGunnar reopened this Mar 20, 2019
@GGunnar GGunnar added the Epic Used by zenhub to identify the epics that group issues. label Mar 20, 2019
@GGunnar GGunnar modified the milestones: MVP.2, MVP Mar 20, 2019
@GGunnar
Copy link

GGunnar commented Mar 20, 2019

Need to discuss this one, related to #1103 which is under development.

@GGunnar GGunnar modified the milestones: MVP, MVP.3 Apr 2, 2019
@GGunnar GGunnar modified the milestones: MVP.3, Post-MVP VIP Aug 28, 2019
@GGunnar GGunnar modified the milestones: CD - phase 1.1, CD - phase 1.3 Nov 5, 2019
@lvbachmann lvbachmann modified the milestones: 2020-May, 2020-June Apr 29, 2020
@lvbachmann lvbachmann modified the milestones: 2020-June, 2021 and beyond Jun 16, 2020
@lvbachmann
Copy link
Contributor

All issues in Epic closed. Thus closing Epic.

@lvbachmann lvbachmann added the skip-releasenotes Issues that do not make sense to list in our release notes label Aug 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ui-editor Area: Related to the designer tool for assembling app UI in Altinn Studio. Epic Used by zenhub to identify the epics that group issues. kind/user-story Used for issues that describes functionality for our users. skip-releasenotes Issues that do not make sense to list in our release notes status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design.
Projects
None yet
Development

No branches or pull requests

5 participants