Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


need some help on the triggers

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Nov 08, 2023

As a team we want to apply the same changes to different version of the release, once the ticket are done for one version and if I work on the ticket for another version in different sprint , the ticket status that was marked as "Done" in previous sprint gets reopened

I have also check on the triggers and its post function but I am not sure why is this causing , can the team help me 

currently done tickets are being reopened when the changes link to that particular tickets are merged into another versions.


1 answer

0 votes
Oday Rafeh
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 08, 2023

Hi @Saran, Welcome to the community : 

Let's troubleshoot and try to resolve this issue together with these steps:

Step 1: Let's start by reviewing any automation rules that may be triggered when the code is merged. Look for any rules that might change the status of an issue or transition it based on specific conditions, such as commit messages or branch names.

Step 2: Next, let's inspect the post-functions on the "Done" transition in your Jira workflow. These post-functions can perform additional actions after an issue moves to a new status, and one of them might be the reason for re-opening issues.

Step 3: It's also important to check the versioning logic in your workflow or automation rules. If it links ticket statuses to specific versions, make sure it can handle multiple versions correctly. The logic should be able to distinguish between different tickets.


Let me know the result, please. 

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Nov 08, 2023

Thanks @Oday Rafeh for the inputs , 

Step 1: there is no triggers set when we merge code 

Step 2: I only see a generic event that is configured . Fire a Generic Event event that can be processed by the listeners 

Step 3 :I couldn't find the versioning in the workflow. Could you pls help me guide on this , or the steps


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events