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!


DevOps automation not apply to all issues returned from filters

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 13, 2023

Greetings to all,

Here is the problem:

In our company we have connected Jira with Bitbucket and after a deployment (via pipeline) want to change the state of certain issues to "in review" with Jira automation. After configuring the automation, and validating JQL filter for check if correctly get all the issues, the automation only affects the issues with the same branch of the deployment, and ignoring the other with different related branch. I triend other filters too but it does the same. The number of the issues are only a few, between 5-10 and all of them are in the same project (set on the scope).

What Im missing?

Thanks in advance.

1 answer

Hello Alezam,


Welcome to the forum! It’s great to see your initiative in integrating DevOps automation within your company’s workflow. From your description, it seems like you’re encountering a challenge where Jira automation is only affecting issues linked to the same branch as the deployment in Bitbucket, and not others with different related branches.


Here are a few areas to consider which might help in resolving this issue:


  1. Jira Automation Rule Configuration: Ensure that your automation rule in Jira is correctly set up to trigger for all the desired issues. Sometimes, the rule might be implicitly filtering issues based on the branch information. Double-check if there’s a condition in the rule that restricts the action to issues linked to the same branch.

  2. JQL Filter Accuracy: Even though your JQL filter seems to be fetching the correct issues, there might be nuances in how it’s interpreted within the context of the automation rule. Verify that the JQL query in the automation rule exactly matches the criteria you want.

  3. Branch Naming Conventions: If your issues are linked to branches in Bitbucket, the automation might be getting confused due to branch naming conventions. Ensure that the branch names are consistently linked with the respective Jira issues.

  4. Automation Rule Scope: Although you’ve set the scope to the specific project, double-check if there are any other limitations in the rule configuration that might be preventing it from affecting all relevant issues.

  5. Rate Limits or Quotas: Sometimes, automation actions might be subject to rate limits or quotas, especially if multiple issues are getting updated in a short span of time. Check if there’s any such limitation that’s causing the automation to partially complete.

  6. Logs and Error Messages: Review the logs or any error messages generated by the automation. They can often provide valuable insights into why certain issues are not being updated.


If after exploring these aspects the problem persists, it might be helpful to reach out to Atlassian support or explore relevant forums for specific advice related to Jira and Bitbucket integrations.


I hope this helps, and feel free to share any further details or updates. The community here is always ready to assist!

Suggest an answer

Log in or Sign up to answer