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

As a guardian I would like to be able to create a new week plan so that it is suited to the given citizens week #51

Closed
3 tasks
Tekrus opened this issue Mar 11, 2019 · 2 comments · Fixed by #164
Assignees
Labels
Priority: highest Highest priority, its required and should be the next target
Milestone

Comments

@Tekrus
Copy link
Contributor

Tekrus commented Mar 11, 2019

  • Screen for adding new week plan that contains the following information:

  • Name of weekplan
    
  • Year of the weekplan
    
  • Week number (of the year)
    
  • Pictogram selector (This should use the same pictogram searcher as new activity see #46)
    
  • A button to select a week template (the feature do not require implementation of the week template feature, only the button)
    
  • A button to save
    
  • A BLoC to archieve the functionality, or implementation of existing BLoCs

  • Redirect to show weeks after adding a new week plan

@Tekrus Tekrus added Priority: highest Highest priority, its required and should be the next target Flutter labels Mar 11, 2019
@sipman
Copy link
Contributor

sipman commented Mar 11, 2019

This feature surrounds the ability to click the "+"-button on the "Choose week"-screen and then see a screen from where I can construct a new week. In forming a new week, I should be able to base it of a week template. This feature does NOT include creating the week template part, only creation of a new week, but please ensure that there is a button for this functionality in the feature — referer to the PO-groups prototypes for any UI questions.

Main activities within this feature:

@sipman
Copy link
Contributor

sipman commented Mar 11, 2019

This feature could possible "conflict" with #52 and #50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: highest Highest priority, its required and should be the next target
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants