Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JPD - linked ideas show as "merged into" instead of "merged from"

Ziv Baum
April 4, 2026

I’m seeing what looks like reversed merge-link behavior in Jira Product Discovery and wanted to check whether others have experienced this.

I am merging ideas into a target idea using the native merge flow.

In my case:

  • source idea being merged: CRT-866
  • target idea: CRT-431

In the merge dialog, I explicitly choose:

  • Target = CRT-431

The merge dialog also says that content is copied from the selected ideas to the target idea, which matches what I want.

So my expectation is:

  • CRT-431 remains the surviving idea
  • CRT-866 is merged into CRT-431
  • on CRT-431CRT-866 should appear under merged from

However, after the merge:

  • CRT-431 does remain the surviving idea
  • CRT-866 gets archived / parked as expected
  • but on the linked work items section of CRT-431CRT-866 appears under merged into instead of merged from

That makes the relationship look reversed, even though the merge target was clearly set to CRT-431

I have automations setup after the merge, which this is impacting. 

This is new... merged ideas from a week ago seems to behave as expected. 

 

2 answers

1 accepted

3 votes
Answer accepted
Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 8, 2026

It's a bug, we're looking into it!

Ziv Baum
April 20, 2026

Hi @Tanguy Crusson - happy Monday. Any updates on this one?

Thanks in advance!

Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 20, 2026

We fixed it, we're now rolling out the fix (I don't know if it's a matter of hours or if  it's up to a week - it depends on a number of factors)

Like # people like this
0 votes
Arkadiusz Wroblewski
Community Champion
April 5, 2026

Hello @Ziv Baum 

Since you mentioned merges from about a week ago looked correct, this looks more like a regression than intended behavior. Because it is also affecting your automation, I would raise it with Atlassian rather than redesigning the rule around this.

(Sudden Happened - Bug or Function Change)

As a quick check, you could also test one merge and look at the automation audit log, since the Work item linked trigger exposes {{destinationIssue}} and {{linkType}}. That would at least show whether this is only a UI label problem or whether the link event itself is reversed too. 

Ziv Baum
April 5, 2026

Thanks @Arkadiusz Wroblewski  - yep, the log shows that CRT-431 is handeled as merged from, instead of merged into, and vis versa for CRT-866. Are you experiencing the same?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events