When a Jira Automation rule reads an old field value, returns a blank smart value, or acts on the wrong issue, first identify which problem you have: stale data, the wrong active issue, branch-local variable scope, delayed data, or an empty branch. The fixes are different: re-fetch updated work item data, use {{triggerIssue}} when you need the original issue inside a branch, and check timing, rule scope, JQL, and actor permissions before changing the rule.
Start by identifying the rule context
Before editing a smart value, note whether the rule runs in Jira Cloud or Data Center, what triggered it, whether it is project-level or global, and the order of its branches and actions. Atlassian’s documentation and troubleshooting guidance can be edition-specific; in particular, the “No related issues could be found” article cited below is for Data Center, not a guarantee about Cloud behavior.
As an Amazon Associate I earn from qualifying purchases.
Then name the work item each action is meant to use. In the main rule flow, {{issue}} normally represents the active work item for that flow. Inside a related-issue branch, the active {{issue}} changes to the related work item the branch is processing. Atlassian explains this behavior in its branch documentation and issue smart-values reference.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteWhy is my Jira automation using stale data?
Jira Automation does not necessarily refresh its issue data after an action changes a field. Atlassian says the {{issue}} reference is not updated during flow execution by default; the rule continues to use the values from when the flow originally triggered. The Cloud Refetch knowledge base article describes the cached state at the start of rule execution.
Re-fetch after a change when a later action needs the new value
Insert the Re-fetch work item data action after the action that changes the work item and before the action that reads the changed value. For example, if a rule edits a priority and then uses a smart value to construct a comment from that priority, re-fetch between the edit and the comment. Atlassian notes that reloading issue data can be expensive, so use it at the freshness boundary where the later action needs current data rather than adding it indiscriminately. See Jira automation actions.
What re-fetch cannot fix
Re-fetch addresses stale issue data; it does not change which issue is active, make a branch-local variable visible elsewhere, or make a missing field property available. If the value remains blank after a re-fetch, verify that the smart value names the right property or field ID, that the field is populated in the relevant context, and that the rule can access it. Atlassian’s guide to smart values showing an empty value is a useful checklist.
How do I use the original issue inside a branch?
A related-issue branch changes the active issue context. Within it, {{issue}} refers to the related work item being processed, not the issue that triggered the rule. To read the original trigger item from the branch, use {{triggerIssue}}; for example, log {{triggerIssue.key}} to check its key. The branch documentation explains the distinction, and the smart-values reference lists issue smart values.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallChoose the reference according to the action’s intended target: use the branch’s {{issue}} for the related work item, and {{triggerIssue}} for the original trigger item. Re-fetching does not correct a context mistake.
Why does a variable work in one branch but not another?
Branches are isolated. A variable created inside one branch cannot be read from the main flow or a separate branch. A missing value outside its branch may therefore reflect scope, not stale data. Keep variable creation and use in the same branch, or restructure the rule so the value is created in a scope that can serve the action that needs it. Atlassian documents branch isolation in its branch guidance.
Do not assume an example that captures a value before branching proves that a variable created inside a branch is available everywhere. The variable’s creation point and the action that consumes it must be considered in the actual rule path.
Why is a value still empty after re-fetch?
Some values are produced asynchronously after the trigger or an earlier action. If another Jira process, an SLA calculation, an integration, or user provisioning has not finished, an immediate re-fetch may still return nothing. In the documented SLA example, Atlassian’s recommended sequence is a delay, then a re-fetch, then the action that consumes the SLA value. See Comment with SLA smart value fails in Jira Automation rule.
Use a delay only when the value depends on work that completes later, and make sure the upstream process has had time to finish. A delay is not a general fix for incorrect context, field references, or branch scope.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why does my branch find no related issues?
A branch that finds nothing may have no eligible related issues, may use a JQL query that returns no visible matches, or may run under a rule scope or actor permission that excludes the targets. Check the relationship or related-issue type, query, project coverage, and the rule actor’s ability to browse the target project.
Atlassian’s article about the audit-log message “No related issues could be found” is explicitly for Data Center. Its causes are useful diagnostic leads, but Cloud users should verify the equivalent details in their own rule configuration and execution audit log rather than treating the Data Center article as proof of Cloud behavior: Atlassian Data Center troubleshooting article.
Debug the exact path in the audit log
- Log the context before the suspected step. Add a Log action that prints the issue key and the exact smart value or field under investigation. In a branch, log both
{{issue.key}}and, if relevant,{{triggerIssue.key}}. - Log again after the change or re-fetch. Compare the value before and after the freshness boundary. This helps distinguish an old value from a property that is blank or unavailable.
- Inspect the execution audit log. Confirm that the expected action ran, which branch ran, which issue it targeted, and what the log output contained. Atlassian describes the Log action among its automation actions.
- Test with one known work item. Use a case where the initial and changed values are distinct, making it easier to see whether the later action received fresh data and the correct issue context.
Keep log output to the minimum needed to diagnose the rule. Avoid putting sensitive personal or customer information in logs that may be visible to a broad audience.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Choose the fix that matches the failure
| What you observe | Likely cause to check | Appropriate next step |
|---|---|---|
| A later action reads the value from before an earlier edit | Issue data was not refreshed during the flow | Re-fetch work item data between the edit and the read |
| An action in a branch uses a related item instead of the trigger item | The branch changed the active issue | Use {{triggerIssue}} for the original item |
| A variable is blank outside the branch where it was created | Branch isolation | Use the variable within its branch or restructure where it is created and consumed |
| A field appears only after a later process runs | Asynchronous data timing | Wait for the documented process, then re-fetch before consuming the value |
| A related-issue branch runs but selects nothing | Relationship, JQL, rule scope, or actor visibility | Check selection criteria and permissions; verify behavior in the relevant Jira edition |
These remedies are not interchangeable: re-fetching cannot repair the wrong active issue, and using {{triggerIssue}} cannot make a branch-created variable global.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
