APFJ - February 2024
- Beata Lewandowska
- 1 Summary
- 1.1 New Features
- 1.2 Improvements
- 1.3 Bug Fixes
Summary
In this release, several updates were made to improve functionality and user experience. New features were developed to make the approval path process more confident. Detected API and comment-related bugs were fixed.
New Features
Add action buttons for approve/reject in outgoing email notifications New
Issue notification emails used to require opening the linked Jira ticket (or Confluence page) to take action. The presented feature enables adding action buttons to allow users to take actions “approve” and “reject” directly from the email - Jira will still be opened but their vote will be added automatically.
This option has to be enabled in AP Settings - it’s disabled by default.
This feature is exclusive to internal users and not meant for external users.
Possibility to exclude some users from the approval group New
While creating the definition, an option to exclude users from a group was added. Excluding approval creator was available in previous versions.
Improvements
Improved QA testing improved
E2E testing methods were improved. Additional tests were performed.
Bug Fixes
Fixed deletion of multiple API key records Fixed
The found bug caused disability to delete multiple API key records. It has been resolved, so users can now successfully delete multiple API key records without encountering any errors.
Fixed grouping parallel step comments Fixed
This bug made comments related to parallel steps to be added as standalone entries instead of being grouped under the corresponding parent comment. This disrupts the logical flow of order in which the comments are organized, making it difficult to track the conversation and approval process effectively. Fixing the problem enabled users to track the conversation and approval process more effectively with an organized structure in the discussion thread.