Build: #227 was successful Scheduled with changes by Wyclif Luyima

Build result summary

Details

Completed
Queue duration
1 minute
Duration
2 minutes
Labels
None
Revision
0efc4212b5957bc35acb927151ecb24f32fe2bcf 0efc4212b5957bc35acb927151ecb24f32fe2bcf
Successful since
#206 ()

Code commits

Author Commit Message Commit date
Wyclif Luyima Wyclif Luyima 0efc4212b5957bc35acb927151ecb24f32fe2bcf 0efc4212b5957bc35acb927151ecb24f32fe2bcf Follow up to fix failing upgrade tests - TRUNK-4446
Wyclif Luyima Wyclif Luyima 0e8cda11ba408bfcf558972c07cebd3b9e9e4f2d 0e8cda11ba408bfcf558972c07cebd3b9e9e4f2d Support deriving auto_expire_date from duration and duration units for Drug Orders - TRUNK-4446
TRUNK-4446: Infer drug order auto expire date based on duration and frequency

TRUNK-4446: Use uuid for comparision. Improved javadoc for ISO8601Duration

TRUNK-4446: Changes based on PR comments

* Remove unused constants in map type
* Use uuid of concept source
* Exception when duration code is unknown
* Exception when frequency not provide for recurring interval
* Fix uuid, dates in change set.
* New change set for alter column
* Check for duration and units before infering expire date
* Use getEffectiveStartDate to handle scheduled order

TRUNK-4446: Add preconditions for inserting concept source and reference terms

TRUNK-4446: Move migrations from liquibase-core-data.xml to liquibase-update-to-latest.xml

TRUNK-4446: Validate duration units is mapped to ISO 8601 duration when auto expire date is not set

Follow up to remove concept map uuid restriction and moved logic that checks for durations mappings to DrugOrderValidator - TRUNK-4446

Follow up to fix failing tests - TRUNK-4446

Jira issues

IssueDescriptionStatus
Unknown Issue TypeTRUNK-4446Could not obtain issue details from Jira