Data Entry Statistics

Build: #11 was successful Changes by 3 people

Stages & jobs

  1. Default Stage

  2. Release

    Requires a user to start manually

Build result summary

Details

Completed
Duration
23 seconds
Labels
None
Revisions
Git
47f0ba7504c054520dbe869bb91311d86ceeec42 47f0ba7504c054520dbe869bb91311d86ceeec42
Release scripts
1969d1c2650fc66ab14f5edb4052a329a196f370 1969d1c2650fc66ab14f5edb4052a329a196f370
Total tests
1
Successful since
#2 ()

Tests

  • 0 New failures
  • 0 Existing failures
  • 0 Fixed

Code commits

Git
Author Commit Message Commit date
dbaluku <juniorderrick18@gmail.com> dbaluku <juniorderrick18@gmail.com> 47f0ba7504c054520dbe869bb91311d86ceeec42 47f0ba7504c054520dbe869bb91311d86ceeec42 DATASTATS-4:Data Entry Statistics By Encounter User Provider Can not Retrieved (#8)
Updated the HQL query building to ensure retrieving provider data entry statistics due to changes on provider to encounter mappings for Platform 2.x
Release scripts
Author Commit Message Commit date
Ian <52504170+ibacher@users.noreply.github.com> Ian <52504170+ibacher@users.noreply.github.com> 1969d1c2650fc66ab14f5edb4052a329a196f370 1969d1c2650fc66ab14f5edb4052a329a196f370 Update release-prepare-perform.sh
Hopefully fix the regex issue
Ian <52504170+ibacher@users.noreply.github.com> Ian <52504170+ibacher@users.noreply.github.com> ce18ee46b521ba3039496ba220aeddd4b313c5e5 ce18ee46b521ba3039496ba220aeddd4b313c5e5 Update release script to support semvers (#7)
* Uses a POSIX-compatible version of the regex for identifying semvers
* Reserves the ending -SNAPSHOT for development versions so we don't break the logic that follows

See: https://talk.openmrs.org/t/easing-semver-constraint-on-releasing-modules-from-bamboo/27716/2
Ruhanga <41738040+Ruhanga@users.noreply.github.com> Ruhanga <41738040+Ruhanga@users.noreply.github.com> ab83775184d5fb0f928388fa25ee675b855dd53c ab83775184d5fb0f928388fa25ee675b855dd53c Adding support for alpha versions (#6)

Jira issues

IssueDescriptionStatus
Unknown Issue TypeDATASTATS-4Could not obtain issue details from Jira