Issue Summary

In the Jira workflow, configure the asset post-function to set the value of an object attribute with a predefined value. Subsequently, configure an asset automation rule to update another object attribute value in the event of object creation or update. Thus, when an issue transitions, the post-function updates an asset attribute, and the asset automation is also triggered. However, this consecutive action fail, resulting in a communication breakdown error in the Jira UI while issue transition. Following this error, the creation of any new objects in the schema will be impeded, and the workflow transition will continue to fail. Object creation can later be resolved by restarting Jira.

Steps to Reproduce

1. Create a new schema and object type. Object type name in this example is Demo. Configure two attributes of type Default and type value Date, naming them First and Second. Additionally, configure one more attribute of type Default and type value Boolean, and name it as Third.
2. Create a new Jira Project (Business, Task Management)
3. Create an Assets Object/s custom field:
3.1 Call it "ACF"
3.2 Limit context to the project
3.3 Set the asset object schema to the imported schema
3.4 Set Filter Scope AQL: objectType = "Demo"
4. Create 2 custom fields of type "Date Picker":
4.1 Call them "Date 1" and "Date 2"
4.2 Limit context to the project
5. Add all 3 custom fields to the screens of the new Jira project
6. On the workflow transition to "Done", add 3 "Assets Post-Function / Set the value of an object attribute with a predefined value" Post Functions:
6.1 The attribute "First" will be set to ${Date 1} in object/s selected in custom field ACF
6.2 The attribute "Second" will be set to ${Date 1} in object/s selected in custom field ACF
6.3 The attribute "Third" will be set to false in object/s selected in custom field ACF
7. On the workflow transition back to "To Do", add 3 "Assets Post-Function / Set the value of an object attribute with a predefined value" Post Functions:
7.1 The attribute "First" will be set to ${Date 2} in object/s selected in custom field ACF
7.2 The attribute "Second" will be set to ${Date 2} in object/s selected in custom field ACF
7.3 The attribute "Third" will be set to true in object/s selected in custom field ACF
8. Create an Insight Schema Automation (Configure Schema -> Automation):
8.1 Call it "Assets Automation"
8.2 Triggered rule will run as "Logged in user"
8.3 Trigger on "Object created" + "Object updated"
8.4 Condition: objectType = Demo
8.5 Then:
8.5.1 Action: Attribute Value
8.5.2 Attribute Name: Name
8.5.3 Value: John
9. Create an issue in the new project, select any of the 2 Demo objects and set 2 arbitrary dates
10. Transition the issue back-and forth between "Done" and "To Do"
11. Issue transition fail with error - Communication breakdown

Expected Results

The expected result is that during the workflow transition, the asset post-function should update the attribute values. Eventually, when the object is updated with the post-function, the automation rule should trigger and execute the rule.

Actual Results

When both assets post-function and assets automation are configured back to back, a communication breakdown error occurs during the ticket transitioning process. New objects cannot be created in the schema until Jira is restarted.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: