Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Starting this page for scoping - Annie Martin to add initial detail.



Responsible Person:
Other parties to review/input:
FYI:
Targeted release date:
Jira Legacy
serverSystem JIRA
columnssummary,fixversions
maximumIssues20
jqlQuerykey in (RVL-142,RVL-141,RVL-124)
serverId3420e60a-4e6f-3f80-8335-059c22bb40aa
Jira Status:
Jira Legacy
serverSystem JIRA
columnssummary,fixversions
maximumIssues20
jqlQuerykey in (RVL-142,RVL-141,RVL-124)
serverId3420e60a-4e6f-3f80-8335-059c22bb40aa

...

  1. Prepare rough business analysis/reqs doc (Christina Riley: IN PROGRESS)
  2. Get CHAI review (DT comment: Christina Riley, I think this feature is straightforward enough to skip CHAI review step, but please indicate there are specific clarifications needed from CHAI, e.g., which fields should be editable vs. non-editable)
  3. Get Akros Review
  4. Get Ona feedback
  5. One iteration
  6. Ona sign off
  7. Ona tech spec scoping
  8. Ona LOE 
  9. Ona scheduling

...

  • Summary: Need editable and non-editable fields
  • Relevant for both Bednet Distribution and Blood Screening forms
  • Mosquito Breeding Site and Mosquito Collection Site forms can be re-completed numerous times and do not require this feature

Requirements

  1. User first has ability to click on any previously completed tasks from the Family Tasks list view to view the previously entered information
  2. Then the user has to hit an "Edit" button to edit those values
  3. Need editable and non-editable fields (Christina Riley: please identify)

Views

We anticipate the following views to be impacted on with the creation of this feature:

...

Justification


Dependencies

  • Data dictionary update (DT comment: assuming may be easiest to define which fields should be editable vs. non-editable in the dictionary)


Questions


Test Case


#

Step

Pass / Fail

Comment

1




2




3




4




5




6




7




8




Additional tester comments:








...