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

UI Structure: NumberWithUnitsInteractionView [Blocked: #150] #152

Open
BenHenning opened this issue Sep 20, 2019 · 3 comments
Open

UI Structure: NumberWithUnitsInteractionView [Blocked: #150] #152

BenHenning opened this issue Sep 20, 2019 · 3 comments
Labels
enhancement End user-perceivable enhancements. Impact: Low Low perceived user impact (e.g. edge cases). Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Priority: Essential This work item must be completed for its milestone. Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@BenHenning
Copy link
Member

This is tracking implementing the initial UI structure of the number with units interaction being fully implemented in #30.

@BenHenning BenHenning added Type: Improvement Priority: Essential This work item must be completed for its milestone. labels Sep 20, 2019
@BenHenning
Copy link
Member Author

This is blocked on #118 for interaction with the domain layer, and #150 for the initial interaction UI structure.

@BenHenning
Copy link
Member Author

This should be a fast-follow item; we cut it from the prototype timeframe.

@rt4914 rt4914 added this to the Global Availability milestone Feb 9, 2021
@Broppia Broppia added Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). issue_type_feature labels Jul 24, 2022
@BenHenning BenHenning added Impact: Low Low perceived user impact (e.g. edge cases). Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Z-ibt Temporary label for Ben to keep track of issues he's triaged. issue_user_learner and removed Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). labels Sep 15, 2022
@BenHenning BenHenning removed this from the Global Availability milestone Sep 16, 2022
@BenHenning BenHenning moved this from Todo to In Progress: Needs mocks in [Team] Core Learner and Mastery flows & UI Frontend - Android Sep 20, 2022
@BenHenning BenHenning moved this from In Progress: Needs mocks to In Progress: Being implemented in [Team] Core Learner and Mastery flows & UI Frontend - Android Sep 20, 2022
@BenHenning BenHenning moved this from In Progress: Being implemented to Todo in [Team] Core Learner and Mastery flows & UI Frontend - Android Sep 20, 2022
@seanlip seanlip added enhancement End user-perceivable enhancements. and removed issue_user_learner labels Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement End user-perceivable enhancements. Impact: Low Low perceived user impact (e.g. edge cases). Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Issue: Needs Clarification Indicates that an issue needs more detail in order to be able to be acted upon. Priority: Essential This work item must be completed for its milestone. Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Development

Successfully merging a pull request may close this issue.

5 participants