Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


How to Resolve "No changes were pulled in from Jira a Jira Align update waiting to be pushed to Jira

The behavior described in this document is foundational to Jira Align, hence it can be noticed in both Standard and Enterprise editions, and it can’t be altered.


This article describes how to proceed when a Jira Align work Item (e.g. a Story or a Feature) is not syncing with Jira anymore, and the following error message can be seen in its audit log:

By External System on <date> <time>
No changes were pulled in from Jira because there is a Jira Align update waiting to be pushed to Jira.

Screen Shot 2022-09-20 at 9.51.09 AM.png


This error is basically caused by a data sync concurrence between Jira and Jira Align.

The Jira Align Connector wrongly determines that its work item's data must be pushed from Jira Align to Jira first, when in fact, the data must be brought to Jira Align from Jira in the first place. That sync concurrence prevents the work item data exchange between the two tools, throwing the error in the audit logs until it gets fixed.

Root cause

There is one known issue that leads the Jira Connector into that situation. It is:

Jira Align work item’s Program and Jira Project fields do not match with Jira Connector’s Jira Project and Program mapping

Take for example when we need to change the Program assigned to an already integrated Jira project that has already several work items (Stories, Features) already synced properly. Also, when you move currently integrated Jira work items between Jira Projects and you must adjust Jira Align Project to Program mapping.

This concurrence match may happen due to a migration/change of a Project to Program mapping on the Jira Connector’s settings in addition to not pushing sync data for all the work items related to this Project from the Jira to Jira Align direction (and not the opposite) right after.

If after this change Jira Align pushes data to Jira’s Work items before Jira does, then all of the related work items will throw the “No changes were pulled (…)" error entry, and block their subsequent syncs.

How to Fix

In the case presented above, you may encounter a scenario like this:

  • The Jira Align work item (Feature, Story) will have its Program and Project fields not matching with your Jira Connector’s Project to Program mapping on Jira Align > Administration > Jira Settings > Manage Projects tab.




Correcting the work item’s Program would fix the problem, however, the Primary Program field is blocked for manual changes, so for these cases, we recommend disabling the sync from Jira Align to Jira, and forcing a sync from Jira to Jira Align:

How to disable Jira Align to Jira work item sync, then force sync from Jira to Jira Align
  1. Log in to Jira Align as Super Admin

  2. Browse to Jira Settings (:coggmail: Administration > Jira Settings > Jira Setup tab), then update the following settings accordingly:

    1. Prior to making these changes, take note of the current settings (you’ll need them later, for configuration restoration)

    2. Allow feature (jira epic) sync from Jira Align to Jira = Jira to Jira Align sync
    3. Allow story sync from Jira Align to Jira = Jira to Jira Align sync
    4. Allow Jira to overwrite Jira Align if two simultaneous syncs conflict = YES
    5. Save settings

  3. Browse to Jira Settings (:coggmail: Administration > Jira Settings > Jira Integration tab), then fill in the following fields accordingly, as we’ll run a custom JQL to pull the stories/features from Jira:

    1. Projects field: inform the affected work item’s Jira Project

    2. AND constraint: fill in with the following custom JQL query

      issuetype = Story OR issuetype = Epic
    3. Leave Run Board field empty

    4. Select No in the corresponding dropdown

    5. Hit the Run button to commence sync

    6. Refresh the page then check the timestamp near the Run button to see how the sync is progressing (clicking browser's refresh button is good enough)
    7. bf800a73-06bc-45f2-82ff-30c52c0ca4d1.png
  4. When the "Last Run (…)” message is seen, that means the Custom JQL is done
  5. Revert Jira Connector settings to the previous configuration (noted in step 2.a)
  6. The affected work items should now get synchronized as expected

How to avoid that sync concurrence?

To avoid this scenario you must follow only one rule:

After updating a Jira Align Program or after a Jira work Items project migration, do not sync or update any related work items data from Jira Align to Jira direction.

Wait until the connector automatically syncs and pushes the data from Jira. Hence it will recognize the Program/Project changes and update all the Jira Align work items according to the new Program/Project Mapping

In addition, you can also execute a Custom JQL query right after, forcing the work items to sync data coming from Jira in the direction of Jira Align.


  • Children’s Stories linked to a Feature in the scenarios above may cause the Stories also face this error.
    Fixing the Feature will as result fix the stories as well.

  • In case you need further support, or the solution presented didn’t work, feel free to open a ticket with us


Allan Silva
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 20, 2022

Excellent article!  Thanks for sharing

Like Victor Fragoso likes this

Tried these steps but it didn't resolve the problem, unfortunately.

Like # people like this
Allan Maxwell
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 29, 2023


Like Rodrigo Cortez likes this


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events