We recently upgraded to Herzum Version 2.9-GA-6.0-6.4 and now all of the tasks linked to existing approval workflows are no longer working. The approval request button is never enabled, the only way to get it to show up is to manually edit each task and set the approval workflow. Please advise as to whether this issue has been reported and the estimated date that a fix will be available.
Can you please check the Status of your Approval Mappings?
If you don't display the green icon as showed on the following screenshot you can fix the issue by following the guide lines illustrated on https://chicago.herzum.com/confluence/display/HAP/Configure+an+overall+Approval+Mapping
Please, let me have your feedback.
The status of the approval workflow is active, yet when work items enter the defined status, the approval feature does not enable. I will mention, this is only happening on work items in flight when we upgraded. Newly created work items are not experiencing the same problem.
until now any attempt to reproduce the bug has not been successful.
On your last comment you said that 'this is only happening on work items in flight', can you please better explicate?
We need further information to be able to reproduce it.
As first, we need the screenshots of an issue were the bug is reproduced, the associated mapping and the approval configuration.
Additional helpful information consist of: used Database, Database Collation setting, Approval Logs when displaying the affected issue.
I have done additional testing and I'm finding that this issue is occurring across both issues that were in progress at the time of the upgrade as well as newly created issues.
I've attached a copy of a document with screen shots that illustrates the issue that I'm encountering.
we have reproduced the issue by forcing an unexpected value Null (expected 0) stored on the Database for the field IS_LOCKED belonging to the table AO_D195E9_APPROVAL_MAPPING.
I need you validate this scenario to fix that.
Can you please have a check on values stored in the fields IS_LOCKED and IS_DRAFT belonging to the table AO_D195E9_APPROVAL_MAPPING table?
Additional helpful information consist of: used Database and Database Collation.
If it is the scenario you are encountering, it can be immediately fixed by following the steps below:
When the mapping status turn to be Valid, review the approvals on the already existing defected issue and on the new one created associated to the specific mapping, we expect that them should be displayed as expected.
Please, let me have your feedback.
Thanks Antonella. The immediate fix that you provided worked for us. The additional information you requested is below:
1. Values stored in the fields IS_LOCKED and IS_DRAFT belonging to the table AO_D195E9_APPROVAL_MAPPING table? NULL or 0
2. Database Used SQL Server 2008
3. Database Collation SQL_Latin1_General_CP1_CI_AS
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
This September 6-7, hundreds of Atlassian App developers will flock to Barcelona Spain to build skills, discover product roadmaps, meet face-to-face with the Atlassian team, and learn how to extend t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs