You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Perhaps and hopefully I'm missing something simple but I'd like to keep the JSM first issue opened and all incoming issues recognized as duplicates, through automation, linked and closed. Currently, I get the opposite - all past issues that are duplicates get closed as they come in and the most recent duplicate stays open.
This is counter to our developer actions where with unique ticket A being read and acted upon, we naturally would like to keep this ticket open since there are actions, history notes being recorded in this tickets fields. We dont want this original ticket A being closed just because a duplicate issue B enters the system. We want the duplicate B ticket closed and the master ticket A left open. I believe "Link Issue to Trigger Issue" (or "most recent") is my problem but I don't see any other option.
The rule below needs adjusting, any suggestions?