Synchronizing Requirements with Jira
Jira Sync enables seamless synchronization of requirements between WalnutAI and Jira, ensuring both platforms remain up to date without manual effort. You can configure one-way or two-way synchronization based on your workflow, allowing requirements to be pulled from Jira, pushed from WalnutAI, or synchronized bidirectionally in real time. This helps maintain consistency, improves collaboration between business, development, and QA teams, and eliminates duplicate work.
Steps for Jira Synchronization
Navigate to Admin Settings

Select the 'Jira Sync Configuration' option.

Select the WalnutAI project that is connected to Jira.

Choose the required sync direction:
WalnutAI → Jira: Enable Push changes to Jira to sync requirements from WalnutAI to Jira.
Jira → WalnutAI: Enable Pull changes from Jira to import requirements from Jira into WalnutAI.
Bidirectional Sync: Enable both toggles to keep requirements synchronized between Jira and WalnutAI.

Click Sync, then select Start Sync to begin the synchronization.

Monitor the real-time sync progress using the Pulled from Jira and Pushed to Jira progress indicators.
Once the sync is complete, review the synchronization summary showing the total number of items pulled and pushed.

Navigate to Action Items in WalnutAI to view the synchronized requirements. The same requirements will also be available in Jira.

With Live Sync enabled, any new or updated requirements created in either WalnutAI or Jira will automatically synchronize with the other platform.
To disable Live Sync, return to Admin Settings and turn off the required sync toggle.

Delete Behaviour
WalnutAI provides three options for handling deleted requirements during synchronization:
Unlink – Removes the association between WalnutAI and Jira without deleting the Jira issue.
Transition to Done/Closed – Marks the linked Jira issue as Done or Closed instead of deleting it.
Delete Jira Issue – Permanently deletes the linked Jira issue when the requirement is deleted from WalnutAI.

Choose the delete behavior that best matches your team's workflow before enabling synchronization.
Last updated

