Cross space/project field synchronization not working

[Jack Wilkins]

Use Case:  Create a flow that performs a cross Space/Project Update triggered by a field change in Space/Project ABC.  When a specific field, SyncSource, in Space ABC (typical JIRA space) changes, it triggers a corresponding change to a specific field, SyncTarget, in Space XYZ (a JPD space).

Issue: The flow does execute successfully however it does not seem to return a list of records from the JPD space that matches the JQL criteria. 

Details:

I’ve tried executing the flow with the scope set to:

• Global
• and Multiple Spaces (where I specified the two individual spaces)

 Actor config:

• The flow actor is set to me.  I’m an admin for both spaces.

Audit log:

• Prior to flow execution it shows
  •  Scope of “Multiple Spaces”
  • Status of “Config Change”
• Executing the flow:
  • Scope of “Name of a single space” (expected this to show multiple spaces)
  • Status of “Success”

 If I tweak and manually run the JQL it does return the expected result set.

For example:

• Original JQL: issue in linkedIssues("{{issue.key}}")
• Tweaked JQL: issue in linkedIssues(ABC-1234)

Result set:

• Two records located in the target JPD space

 

Sample of the current flow:

Trigger (based on field in JIRA space ABC)

└─ Field value changed

└─ Field: SyncSource

Lookup Issues (query across all spaces)

└─ JQL: issue in linkedIssues("{{issue.key}}")

Advanced Branching (operates on record set from above)

└─ Variable name: linkedIssue

└─ Smart value: {{lookupIssues}}

Edit Issue Fields (updates result set from JPD spaces)

└─ SyncTarget = {{issue.SyncSource}}

[Arkadiusz Wroblewski]

Hello @Jack Wilkins 

First Question, and i asking that without really reading Automation as it will be thing for Later. Did it worked before, or Started to make Problems just Suddenly ?

We have some Problems from Yesterday around Automations so it could be related.

status.atlassian.com 

Best,

Arek🤠

[Jack Wilkins]

Hello @Arkadiusz Wroblewski ,

This is a brand new flow.

Jack

[Arkadiusz Wroblewski]

Try this

Trigger
└─ Field value changed
└─ Field: SyncSource

Condition
└─ Space/project equals ABC

Branch rule / related work items
└─ Linked work items
└─ Select the relevant link type, or all link types

Condition
└─ Space/project equals XYZ
Optional: Work type equals Idea

Log action
└─ Source={{triggerIssue.key}}
Target={{issue.key}}
Value={{triggerIssue.customfield_12345}}

Edit work item
└─ SyncTarget={{triggerIssue.customfield_12345}}

[Jack Wilkins]

Thank you for the suggestion.  Unfortunately, I get the same results.

The messages in the log are the same as I previously got:

• Scope: Project A
• Issue key is ABC-1234 
• JQL Condition
  • The following issues did not match the condition:

ABC-1234

• The work item didn't match the specified JQL.
• The chosen flow actor doesn't have permissions (or work item security level permissions) to view the work item.
• the work item was deleted or wasn't indexed by Jira yet (in rare circumstances)

We recommend using the 'Issue fields condition' for more consistent results.

Any thoughts?  BTW, our system is using the "newer" flow UX.

Thanks - Jack