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

User Story 3.6 #54

Closed
NicholasNagy opened this issue Oct 18, 2020 · 0 comments
Closed

User Story 3.6 #54

NicholasNagy opened this issue Oct 18, 2020 · 0 comments
Assignees
Labels
User Story informal, natural language description of one or more features of a software system.
Milestone

Comments

@NicholasNagy
Copy link
Member

NicholasNagy commented Oct 18, 2020

User Story: ALTA-3.6

As an inventory manager, I want to be able to schedule automatic audits at a specified frequency so that I can routinely reinitiate audits.

Description:

  • Inventory managers want to be able to schedule audits at some interval so that they don't have to manually initiate an audit whenever they think an audit should be scheduled.
  • This should be implemented in the same fashion as the inventory loading mechanism that Robert had implemented for user story 2.4 (User Story 2.4 #47).

Acceptance Criteria (AT-3.6 #223)

Given that the user is logged in as an inventory manager,

  1. The user should be redirected to the Dashboard page.
  2. The user selects the Template side menu option.
  3. The user is presented with the organization's predefined templates (if any) and an Add button.
  4. The user selects the Add button.
  5. The user is presented with an empty form containing the template's input fields and scheduling sub-section.
  6. The user inputs the template information and schedules the audit's start date, start time, recurrence, and time zone.
  7. The user selects the Save button.
  8. The user is redirected back to the Templates page to confirm the template creation.

Related Mockups:

  • Inventory manager login page

log in

  • Template page accessed from side nav

Below scheduling, user can define the start date and time, even the recurrence and regarding which time zones
Capture d’écran 2021-01-28 à 16 39 44

When the recurrence field is clicked
Capture d’écran 2021-01-28 à 15 51 21

@NicholasNagy NicholasNagy added this to the Sprint 5 milestone Dec 7, 2020
@NicholasNagy NicholasNagy added User Story informal, natural language description of one or more features of a software system. and removed Developer Story labels Dec 7, 2020
@Amanda-Kolopa Amanda-Kolopa modified the milestones: Sprint 5, Sprint 6 Jan 26, 2021
NicholasNagy added a commit that referenced this issue Jan 31, 2021
Issue #54 - User story 3.6 - Scheduling audits
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
User Story informal, natural language description of one or more features of a software system.
Projects
None yet
Development

No branches or pull requests

4 participants