Write field on linked issues problem with assignee field
We are having a strange issue when changing the target assignee field from a linked issue. Target issue history records the change, however the actual value is not changed.
atlas AIMS Administrator made changes - 6 minutes ago
Assignee GEO-GD [ aims-sample-expert ] ATP-ATP [ atp ]
atlas AIMS Administrator made changes - 6 minutes ago
Responsible ATP-ATP [ atp ]
Assignee is still "GEO-GD". On the contrary the User Picker CF works fine "ATP-ATP".
Any ideas?
Comments (19)
-
reporter -
repo owner Ok, I keep waiting for your news.
-
reporter It's rather complicated as it involves Workflow Toolbox, Script Listener and Automation:
- The post-function updates the assignee field on a linked issue (another pf also triggers a transition through delayed status change)
- A script (runner) listener is configured to catch "ISSUE_UPDATED" and "ISSUE_ASSIGNED" events, checks if the assignee field was changed and then triggers a custom event, e.g. "SYNC_EVENT".
- A JIRA Automation rule, catches the "SYNC_EVENT" and performs several actions (one of them triggering a workflow action).
- If only the first step is enabled everything works fine.
- If the automation rule (configured both with synchronous or asynchronous execution) the assignee field is not updated, although history says so.
- If we setup the listener to directly trigger the workflow action, instead of going through the custom event etc., the update works fine as well.
We've initially opted for JIRA Automation for additional flexibility (more actions etc.) however from the above I believe it should be the cause of the update problem. What do you think?
Cheers, Aggelos
-
repo owner Please, attach screenshots of the configuration of all the elements implied in this problem:
- Post-function's tab of the transition which executes workflow toolbox post-functions.
- JIRA Automation rule.
- Listener configuration.
- Post-function's tab of the transition executed by the listener.
-
reporter - attached sync-task-pf.png
- attached pf-part1.png
- attached script-listener.png
- attached pf-part2.png
- attached automation-rule.png
-
reporter I've kept the post-functions on the transition (sync-task-pf.png) executed by the listener (or automation rule) to the bare minimum just to minimize the possible side-effects. The problem is still there.
-
repo owner Can you, please, tell me why are you executing "Sync Task"? It seems to do nothing.
Please attach a screenshot of post-function's tab of "Start Progress" transition.
-
reporter - attached start-progress.png
Hi Fidel,
For the first part of your question I've posted a note before. I purpose I kept it "Empty". Attaching the "Start Progress" PFs. Although I don't believe this is the cause, because in same cases it isn't executed as the target issue is not in "To do" status.
-
repo owner Can you please execute JIRA Integrity Checker? Please, let me know what you find.
-
reporter "No errors were found."
-
repo owner Hi Aggelos, sincerely I can't find a reason for that behavior. Anyway, can you please try the following:
1) Add a "Boolean condition with math, date-time or text-string terms" with the following boolean expression:
false
2) Set parameter "Skip condition checking" to false.
I would like to see if not executing transition "Sync Task" makes any difference.
-
reporter Hi Fidel, Same behavior. Really strange.
-
repo owner If you remove "Transition Issue Action" from Automation rule the problem disappears, isn't it?
-
reporter No, this is the strange thing. Even if I only leave an "Add Comment" action, the problem is still there.
-
repo owner Hi Aggelos, which version of JIRA and Script Runner are you using? I'm going to try to reproduce your problem.
-
reporter Hi Fidel,
ScriptRunner 4.3.0 JIRA 7.1.4 JIRA Automation 2.0.0
-
repo owner Hi Aggelos, I have achieved to reproduce your problem. Now, I will try to find the cause and fix it if it depends on JIRA Workflow Toolbox.
-
reporter Or raise a few bug reports on other components. They seem to listener to you and fix them quickly.J
-
repo owner - edited description
- changed status to wontfix
Hi Aggelos, I close this issue, since it doesn't seems to be caused by JWT.
- Log in to comment
I believe I found a possible root cause. Please don't bother investigating for now. I'll come back with details later on.
Cheers, A.