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.
Join now to unlock these features and more
Updates from Jira are not flowing over to Jira Align. Receiving Message in Audit logs.
No changes were pulled in from Jira because there is a Jira Align update waiting to be pushed to Jira.
What do I need to do to fix this issue?
@Peter Jessen I bet you have an answer...
Hi @Ann Bouvier ,
This is related to the Allow Jira to Overwrite Data setting in Administration -> CONNECTORS -> Jira Settings -> Jira Setup tab.
The reason for this situation is because the connector "sees" a change on a feature/story in Jira Align that hasn't pushed to Jira, while at the same time someone made a change to the same feature/story in Jira. Allow Jira to Overwrite Data is probably set to No, therefore someone must manually resolve the issue.
One (safe) way to resolve this:
As I said, the above is a safe option.
To avoid this issue in the future:
HI Everyone and HELLO Peter!
Peter is absolutely correct about the answer he provided, but I would like to provide more clarity on the scenario he used as an example of when data might not flow.
Peter had suggested that replication may not occur between JA and Jira "...because the connector "sees" a change on a feature/story in Jira Align that hasn't pushed to Jira, while at the same time someone made a change to the same feature/story in Jira."
While this scenario is hypothetically possible, it is improbable due to the timestamping of records in Jira history and JA. The more likely culprit is that certain transactions in Jira simply do not update the "Jira Update Timestamp field" that JA uses to determine if the record(s) need replicated. For example, updating a hyperlink in Jira does not actually update the Jira DTS as one might expect. There are in fact numerous transactions, due to the way Jira is designed that can sneak through without a DTS update.
One way to check if this is the case, assuming all other replication conditions are being (e.g. the sprint or story isn't shared across jira boards), is to simply attach a new jira label to the object. If this causes the record to replicate, you may have found the culprit.