Versions Compared

Old Version 1

changes.mady.by.user Victoria_Smelova

Saved on

compared with

New Version Current

changes.mady.by.user Denis

Saved on

Key

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

...

groom.Assignee: NoneIn Review
  • Story/bug to be reassigned to PO
    • Assignee: PO (or Back-end Lead for back-end storiesBack-end Story/Bug: the API Tests should be run from master branch or a branch with prepared PR to make sure no regression introduced and new tests meet Acceptance Criteria. If all is okay, the PR is approved and merged to master. with a comment.
    JIRA StatusDescriptionAssignee/Actions
    DraftPO is defining the user story. Not ready for the team to review.

    Assignee: PO (or Back-end Lead for back-end stories)

    • Requirements to be finalized and added to story/bug
    • Story/bug to be updated according to the templates
    Open
    In RefinementReady for refinement/grooming

    Assignee: None

    • Issue is better defined and ready for the development team to review and to
    • estimate issue.  
    • Story/bug to be reviewed and discussed on Backlog Grooming
    • Requirements to be clarified
    • Acceptance criteria to be understood
    • Estimation to be added
    OpenReady for development 

    Assignee: None

    • Story/bug to be taken into development
    In ProgressDevelopment is in progress

    Assignee: Developer

    • Requirements to be turned into working software
    • Acceptance criteria to be met 
    • Tests to be added/updated to ensure 80% coverage
    • Dev verification to be done
    • Critical defects to be addressed
    BlockedDevelopment is blocked

    Assignee: Developer/PO

    • Blocker to be linked in JIRA via "is blocked by" (if any)
    • Comment to be added to clarify what the blocker is (in case there is no blocking story)
    In Code ReviewPR is done and Code Review is in progress

    Assignee: Developer

    • PR to be reviewed by other developers
    • Comments provided in GitHub to be addressed
    • 2 approves of a PR are preferable
    • PR to be merged
    • required
    • PR to be merged

    In QA (new optional state)

    FOR UI non-technical tickets only

    		PR is merged and updates are ready for verification by QA team

    Assignee: Developer

    Assignee: Quality engineer

    • UI Story/Bug to be carefully verified on https://folio-snapshot.dev.folio.org/ OR https://folio-snapshot-2.dev.folio.org/ (based on availability of changes)
      • Story to be moved to 'In Review' if requirements are met and result conforms AC of the ticket
        • PO must be tagged that a story is ready for final review (if an item can be verified by PO)
      • Story to be moved back to 'In Progress' in case the requirements are not
        • comment/screenshot to be added with comments on the issues found
    In Review (current)PR is merged and updates are ready for review

    Assignee: Developer

    Assignee: Developer or Unassigned (for items that can not be verified by PO for double verification)

    • Story/Bug to be checked on https://folio-snapshot.dev.folio.org/ OR https://folio-snapshot-2.dev.folio.org/ 
      • stories are checked and accepted by PO
      • technical stories that can not be verified by PO are checked and accepted by any available developer and should be assigned to a dev as soon as they are picked up for final verification and acceptance.
    • Story to be closed if requirements are met and it conforms to the definition of done
    • Story to be reassigned back 'In Progress ' to the developer (implementer) in case the requirements are not met
    • Additional stories to be created in case additional requirements/updates are identified while review
    Obsolete - In Review (old)PR is merged and updates are ready for review

    Assignee: Developer

    • PO must be tagged that a story is ready for verification (if an item can be verified by PO)

    Assignee: Developer or Unassigned (for items that can not be verified by PO for double verification)

      • stories are checked and accepted by PO
      • technical stories that can not be verified by PO are checked and accepted by any available developer and should be assigned to a dev as soon as they are picked up for final verification and acceptance.
    • Story to be closed if requirements are met and it conforms to the definition of done
    • Story to be reassigned back to developer (implementer) In Progress in case the requirements are not met
    • Additional stories to be created in case additional requirements/updates are identified while review
    Awaiting release

    Applicable for the fixes to be included into Bugfix or Hotfix releases.

    Fix is ready to be included into Bugfix or Hotfix release.

    Assignee: Developer

    • Fix was tested and accepted by PO on testing/snapshot env 
    • Fix is waiting to be included into Bugfix or Hotfix release
    Awaiting deployment

    Applicable for the fixes to be included into Bugfix or Hotfix releases.

    Fix is included into Bugfix or Hotfix release and is waiting to be deployed to corresponding BugFest env.

    Assignee: Developer

    • Fix was included into a Bugfix or Hotfix release
    • Release was announced in Slack
    • Corresponding release tasks (linked to the fix) was closed
    • Status was updated to Awaiting deployment by SM upon release announcement
    In Bugfix Review

    Applicable for the fixes to be included into Bugfix or Hotfix releases.

    Fix is deployed to corresponding BugFest env in scope of a Bugfix or Hotfix release.

    Assignee: Developer/PO

    • Fix was deployed to a corresponding BugFest env as a part of a Bugfix or Hotfix release
    • Status was updated to In Bugfest Review by AntonE
    • Fix is to be tested by PO/Developer on Bugfest env to confirm it is working as expected
    ClosedStory is accepted by PO and closed

    Assignee: PO (or Back-end Lead for back-end stories)

    • Updates can be demonstrated on System Demo

    ...