New feature
One new feature is now available.
Resolve field
| Status | ||||
|---|---|---|---|---|
|
If the creator of the definition opts to use issue fields, the creator can now decide on when the field must be resolved, in other words, evaluated and revealed.
Under circumstances the custom fields may not be populated or is required to remain hidden at the time of the definition creation, regardless, the approval path must continue!
...
As depicted in the picture, there are now two options to improve the path,
Approval start
Evaluates and reveals the step approver(s) as soon as the approval path starts.
If empty, the user will be notified however the path will be opened and the step will be skipped to the next populated step
If no populated steps exist, the path will not start
Step start
Evaluates and reveals the step approver(s) only once the step is reached.
If empty, the step will be skipped
There may be a merit to ensure this step is not the first on the list as that would evaluate and reveal the step on the start of the approval path
...
Archive / Reset
| Status | ||||
|---|---|---|---|---|
|
We will be keeping a history of started approvals on our end, archiving approvals is now allowed.
...
Bug fixes
| Status | ||||
|---|---|---|---|---|
|
Fixed a bug which caused errors for webhook
When Jira send us notification about Project delete we do cleanup running approvals in that project.
Due to error in some circumstances we did drop this event. Which we fixed.Fixed an issue were Non admin user - given the “View approval path on issue page” permission was able to view ongoing approvals however, user was unable to view filter results while filter results button was present.