-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
Component/s: Trigger - Issue Created
-
None
-
Severity 3 - Minor
-
Jira Software
Issue Summary
This only applies to non-subtasks, because work has already been done to ensure that `issue.parent` is re-fetched for subtasks.
Steps to Reproduce
- Create a rule with an issue updated trigger, and LogAction:
{{issue.parent}}
- Make it fire for a non-subtask (e.g. a Task) that has a Parent issue linked to it.
Expected Results
issue.parent should be logged.
Actual Results
It's blank. But if you add a "Re-Fetch issue data" action before the Log Action, then it works.
Workaround
Add a "Re-Fetch issue data" action immediately after the trigger.
- is caused by
-
PCS-228573 Loading...
-
JPO-18376 Loading...
- mentioned in
-
Page Loading...
- relates to
-
PIR-10398 Loading...