Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
pcmt
pcmt
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 148
    • Issues 148
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pcmt
  • pcmtpcmt
  • Issues
  • #756

Closed
Open
Created Jan 12, 2021 by Josh Zamor@joshzamorOwner0 of 10 tasks completed0/10 tasks

Cron malawi mapping script

User Story

As an implementer I want to be able to set a simple cron schedule on the malawi mapping script so that it runs periodically without anyone having to do anything.

Background Documents

(Insert links to any relevant documents)

Acceptance Criteria

(Describe additional criteria that must be met for the User Story to be complete)

e.g.

  • Whenever the user clicks cancel or tries to go forward or back in the browser they should be asked to confirm before they lose changes.
  • If the user clicks Save any input should be validated so they can't make a mistake

Definition of Ready

  • User Story can be broken down no further
  • Acceptance Criteria and Story Points are agreed upon by development team and PO

Definition of Done

  • If required, UI Mockups are created and reviewed
  • Code is written with automated unit tests, reviewed, merged to master branch, all tests pass
  • All UI texts are multilingual
  • Manual tests in test environment are successfully performed
  • Test Plan is updated
  • Documentation is updated
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None