Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Feedback on Team Assignment functionality added to the WebUI

______________________________________________________________________________________________________________________________________

I now see the following options at the top of my menu:

Click ‘Admin’. See below view:

Click ‘view’ next to a team:

Click edit:

Toggle No-Yes for ‘active’ seems to be working, and the value saves when I ‘save team’ and navigate away and back.

Clicking ‘New Team’ as on first screenshot takes me to same view as edit view.

Click from menu ‘Assign’.

See list of plans that are both FI and IRS (note ‘intervention’ column)

HEADER needs to not read ‘IRS Plan’ since both types appear under this header.

Select an IRS plan:

THIS SCREEN TAKES A LONG TIME TO LOAD -CANT GET IT TO LOAD

______________________________________________________________________________________________________________________________________

Test scenarios to test out:

  1. Volume test

    1. Volume test # spray areas, #tasks, #structures per team

    2. Volume test # users per team

  2. Generic scenarios

    1. Team 1 and Team 2 in different areas on day 1. On day 2 team 1 goes to team 2’s area from previous day.

    2. Test assignment at spray area level - 1 and multiple

    3. Test assignment at catchment level

    4. Test assignment of multiple spray areas in different catchments

    5. Test assignment at district level (? maybe not, might be too big/ no use case ?)

    6. Test assigning users to multiple teams (is this supported for IRS now?)

  3. Zambia-specific scenarios

    1. Mimic 1 district and 1 set of teams in Zambia

      1. Test a day of team assignment - put 3-5 users (TLAs) on a team and assign the team to the areas you think they will go to that day and back up areas

        1. How long does this take to do? (operations)

      2. Test move teams across districts

      3. Test ‘fixed’ team scenarios where each team is linked to a geographic area and you reassign users across teams

  4. Namibia scenarios

  • No labels