Jira development panel information from Bitbucket is not up to date

Stefan Apelqvist_y2yghs

We have Jira and Bitbucket. We can create branch and pull requests from Jira issue, which is very convenient as they are also found by Jira and you can see the status. We use a structure with submodules and therefor it's common that an issue has more than one branch and more than one pull request as a result.

Our problem is that the status of pull requests are not always updated.

When I view the Jira issue it looks like the pull request is open, but if I click on "1 pull request", then I get a list of pull requests and the status shown is merged (which is correct).

We also have a rule to handle transitions to Done and if there are more branches and pull requests, the issue should go back to "In Review". Here is our biggest problem, because the automation rule seams to use the same data source as the issue view and when that is not up to date, the rule will kick the issue back to "In Review" even if all the pull requests are actually merged.

Some day's this is working as a charm, some weeks we struggle and have to manually go through tickets "In Review" and set them to "Done" after the system has updated the status.

Does anyone see a solution to this?

Shatakshi Mete

Here are a few things you might want to check or try:

1. Sync Delays: Sometimes, Jira’s development panel doesn’t update instantly. There can be a delay between Bitbucket and Jira. You might want to check if there's a pattern (e.g., during peak usage times) when this issue occurs.

2. Reindexing Jira: Occasionally, reindexing Jira can help sync up data more accurately. If you have admin access, try doing a reindex or ask your Jira admin if that could help fix the lag in PR status updates.

3. Automation Rule Tweaks: Since your automation rule is based on the PR status, you might want to tweak it to account for this sync issue. You could add a condition to delay the rule trigger, giving Jira more time to update the status. Or, add a manual check step in your workflow to confirm all PRs are merged before moving it to "Done."

4. Webhook Configurations: Double-check the webhook configurations between Jira and Bitbucket. A misconfigured webhook could cause data not to flow properly, leading to outdated information in the Jira issue.

5. Atlassian Support: If the problem persists regularly, it might be worth reaching out to Atlassian support to see if there's a deeper integration issue between Jira and Bitbucket.
   
   

   hopefully, one of these suggestions helps make the process smoother for your team!