Versions Compared

Old Version 23

changes.mady.by.user Sam Im (Deactivated)

Saved on

compared with

New Version 24

changes.mady.by.user Sam Im (Deactivated)

Saved on

Key

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

...

  • The goal of this requirements page is to document the feature of User Management and the associated user stories. User Management is defined as enabling the administrator to create and manage users so that new or existing users can perform normal job duties once the setup and management is complete. 
    • Scope: This feature includes stories on:
      • Creating a new user and assigning a Home Facility.
      • Resetting a password from the user profilelist.
      • Enhancing the usability of the user search functionality from version 2.0

...

#TitleUser StoryImportanceNotes
1Create user

As an administrator I need to enter users into the system so that I can complete the assignment of the required roles, facilities, and programs to each user.

Acceptance Criteria:

  • Once Admin can create and save a user has been created and saved, certain fields should be uneditablenew user.
  • Validation (minimal needed) for each field that is assigned.
Must have
  • 2.0 Design provides a dropdown/preselected list.
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2009
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2105
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2216
2Create password

As an administrator I need to create passwords for users so that they can access the system.

Acceptance Criteria:

  • Admin creates password and manually notifies user.
  • Admin creates User and system sends email with set password link.
Must have
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2106
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2141
3

Edit user information

 As an administrator I need to edit user's details so that I can update the system to reflect changes.

Acceptance Criteria:

  • User search provides a list of available users to edit.
  • Admin can edit user details.
  • Validation (minimal needed) for each field is completed after it has been edited.
 Must have
  • 2.0 Design shows dialog box to enter name for search but a list is preferred.
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2011
4Email Password reset

As an administrator I need to reset a user's password so that I can support a user's access.

Acceptance Criteria:

  • Administrator has ability to select user and send an email that resets their existing password
Must have
  • This is utilized when the user has access to their email address but forgot their password.
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2140
  • Jira Legacy
    serverJIRA (openlmis.atlassian.net)
    serverId448ba138-230b-3f91-a83e-16e7db1deed1
    keyOLMIS-2217


...

  • Mobile user identification when a user is set up. In 2.0 the administrator identifies a user as mobile to allow user creation without an email address.
  • Configuration screens for .csv upload to create initial facilities.
  • Allocation Program based rights and Admin Reports rights will be in a future release.
  • New Supervisory Node creation.
  • Creation and editing of roles will be in a future release. 
  • Reporting updates will be in a future release.
  • Roles and Facilities management are separate features.
  • Offline functionality and saving is out of scope. Admin user must have internet access to complete any of these tasks.