Hi @Kustagi Suma
This should be definitely doable with automation — the trick is getting the rule to look up the sibling stories correctly, not sure if this is your problem though.
The most reliable approach is a rule that triggers when a child issue is created (or linked to a parent), then looks up the other children and creates the links:
- Trigger: Issue created (or "Issue linked" if you're adding children after creation)
- Condition: Check that the issue has a parent:
{{issue.parent}} is not empty
- Look up issues: Use the JQL
parent = {{issue.parent.key}} AND key != {{issue.key}} — this finds all sibling stories under the same parent, excluding the current one
- For each: Create link → "relates to" between the trigger issue and each looked-up issue
A couple of things to watch out for:
- If you're using issue links (e.g., "is child of") rather than the built-in parent field to model the Feature → Story relationship, the JQL in step 3 needs to change. The
parent = JQL only works with Jira's native parent/child hierarchy. For issue-link-based relationships, you'd need a different approach — potentially a "Related issues" branch condition instead of "Look up issues."
- Jira won't create duplicate links, so running this on existing stories is safe — it'll skip links that already exist.
- Make sure the automation has the right scope (project vs. global) to see all relevant issues.
One other thought — if the reason you're cross-linking siblings is to see which stories belong to the same feature, you might not need explicit links at all. If you're open to solutions from the Atlassian Marketplace, JXL for Jira lets you set up a hierarchy view where all child stories appear nested under their parent Feature in a tree structure. You'd see at a glance which stories are siblings without maintaining "relates to" links between them.
Disclosure: I work for the team that builds JXL.
Cheers, Paul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.