From 94d08629d5b5bbc2f5a05fe5e0363252117accb6 Mon Sep 17 00:00:00 2001 From: Aliaksei Chumakou Date: Thu, 12 Dec 2019 15:15:21 +0300 Subject: [PATCH] add changelog --- CHANGELOG.md | 12 ++++++++++++ PULL_REQUEST_TEMPLATE.md | 31 +++++++++++-------------------- 2 files changed, 23 insertions(+), 20 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 49d9946b..4d623577 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,17 @@ # Change history for stripes-acq-components +## [1.3.1](https://github.com/folio-org/stripes-acq-components/tree/v1.3.1) (in progress) +[Full Changelog](https://github.com/folio-org/ui-invoice/compare/v1.3.0...v1.3.1) + +### Stories +* [UIORGS-122](https://issues.folio.org/browse/UIORGS-122) Organization view pane: Update contact people view + +### Bug Fixes +* [UIOR-464](https://issues.folio.org/browse/UIOR-464) Calculation of estimated price in cost details sometimes blocks POLs from being created/saved +* [UIPFPOL-3](https://issues.folio.org/browse/UIPFPOL-3) Return focus after lookup modal is closed without selection +* [ERM-620](https://issues.folio.org/browse/ERM-620) Agreement edit/new: return focus to the lookup button when a lookup modal is closed +* [UINV-94](https://issues.folio.org/browse/UINV-94) Not able to create invoice lines with $0 subtotal + ## [1.3.0](https://github.com/folio-org/stripes-acq-components/tree/v1.3.0) (2019-12-04) [Full Changelog](https://github.com/folio-org/stripes-acq-components/compare/v1.2.0...v1.3.0) diff --git a/PULL_REQUEST_TEMPLATE.md b/PULL_REQUEST_TEMPLATE.md index 8b822fb8..03c9a5d8 100644 --- a/PULL_REQUEST_TEMPLATE.md +++ b/PULL_REQUEST_TEMPLATE.md @@ -1,11 +1,6 @@ ## Purpose @@ -14,7 +9,7 @@ to provide to the reviewer and to future readers than the cause that gave rise to this pull request. Be careful to avoid circular statements like "the purpose is to update the schema." and - instead provide an explanation like "there is more data to be provided and stored for Purchase Orders + instead provide an explanation like "there is more data to be provided and stored for Purchase Orders which is currently missing in the schema" The purpose may seem self-evident to you now, but the standard to @@ -23,7 +18,7 @@ section." If you have a relevant JIRA issue, add a link directly to the issue URL here. - Example: https://issues.folio.org/browse/MODGOBI-43 + Example: https://issues.folio.org/browse/MODORDERS-70 --> ## Approach @@ -35,13 +30,13 @@ developers *work* with your solution in the future. --> -#### TODOS and Open Questions -## Learning