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

3w: Form to capture project details #640

Closed
batpad opened this issue Jun 26, 2019 · 4 comments
Closed

3w: Form to capture project details #640

batpad opened this issue Jun 26, 2019 · 4 comments
Assignees

Comments

@batpad
Copy link
Contributor

batpad commented Jun 26, 2019

We need to implement a form on the frontend for users to enter details of Projects, that will be aggregated on the Who-What-Where frontend on the Country page.

The design for the form is here: https://projects.invisionapp.com/share/P9SA110GT4S#/screens/369905382

Backend tickets to implement models and API.

This form will post to the API we create on the backend and save Projects.

Question on the design: currently, there is a button next to the map on the country page that says Edit that takes you to this form. I'm not sure how that's supposed to work, or if that button should say Add ? If it is meant to be Edit, which Project should they be editing, since there will be many projects? I will clarify this with the design team.

cc @mankamolnar

@batpad batpad self-assigned this Jun 26, 2019
@batpad batpad added this to Goals in IFRC Go Phase 3 Jun 27, 2019
@batpad batpad moved this from Goals to In Progress in IFRC Go Phase 3 Jun 27, 2019
@batpad batpad moved this from In Progress to Goals in IFRC Go Phase 3 Jul 15, 2019
@batpad batpad assigned frozenhelium and unassigned batpad Sep 26, 2019
@batpad
Copy link
Contributor Author

batpad commented Oct 2, 2019

Capturing some changes to the design based on discussion with @guipizzini :

  • Add a field called Type of Operation (radio?) with options Long-term operation and Emergency operation
  • Move Programme Type field to next to or below Type of Operation field
  • Based on selection of Type of Operation and Programme Type fields:
    • if Type of Operation is Emergency Operation and Programme Type is Multilateral, show Current Operation dropdown. Else, do not show. @guipizzini to confirm if Current Operation is to show or not for Emergency Operation that is of Type Bilateral.
  • Split Sector of Activity into two fields:

@frozenhelium @guipizzini - please let me know if I missed capturing anything.

@frozenhelium
Copy link
Member

frozenhelium commented Oct 15, 2019

More changes after discussing with @guipizzini and @LukeCaley

Add following 2 numeric fields

  • People targeted
  • People reached

The field are required only if the project's status is completed.

This can be implemented in 2 ways:

  1. Make these new field required if the status field in project form is set to completed.
  2. Send notification to the user when the project is complete.

@LukeCaley to decide which approach to take

@batpad
Copy link
Contributor Author

batpad commented Oct 15, 2019

@LukeCaley both @frozenhelium and my strong recommendation here would be to go for option 1 for this - when the user updated the status to complete, show the 2 numeric fields for People Targeted and People reached and make these fields required if status is complete.

This will guarantee that we can validate the data and make sure that there cannot be Projects where the status is complete and do not have this data filled out. Overall, this seems to me like it's more intuitive for the user, as well as easier to implement.

@LukeCaley please let know if it's fine to go ahead with Approach 1 - i.e. Make these new field required if the status field in project form is set to completed. instead of going the notifications route.

Of course, there could be details of the work-flow that we're missing, so if it makes more sense to go with the notifications or another approach, we should discuss that soon.

@LukeCaley
Copy link

@batpad Thanks for outlining the options and for the suggested appraoch. Agreed that this should be the logic. Once we have the prototype we will explore user journeys with the module to understand potential exceptions but the suggestion looks good for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

3 participants