Jira Full Sync FAQ

← Back to How ProdPad works with Jira

What is Jira Full Sync?

The Jira Full Sync integration allows Syncing of content in 2 directions between Jira Cloud and ProdPad. With Jira Full Sync, you're able to sync content and statuses between Jira and ProdPad.

How long does it take for my changes to show in ProdPad?

When you push an idea or user story to Jira, the Jira Issue should be created immediately. When you make any changes to a pushed idea or user story in ProdPad and press the Sync updates to Jira button, the changes should appear immediately in Jira. 

Due to the nature of the sync, any updates made to a linked issue in Jira can take up to 15 minutes to appear in the linked idea or user story in ProdPad. The full sync updates run every 15 minutes on the hour, and you should never need to wait longer than this for changes made in issues in Jira to appear in ideas or user stories ProdPad. If 15 minutes have passed and you do not see a content or status update made in Jira show up on the linked idea or user story, please let us know.

What are the current Jira Full Sync capabilities?

The Jira Full Sync integration currently offers the following capabilities:

• Users are able to push an idea (with or without associated user stories) to Jira Cloud and Server/Data Center projects.
  • If the idea is not already associated with a Jira issue, then a new issue will be created of the type mapped during the integration configuration.
  • If the idea is already associated with a Jira issue, that issue will be updated with the changes from ProdPad. It's important to note that at this time, this won't create any new user stories. 
    
• Users are able to push a user story to Jira Cloud and Server/Data Center projects..
  • If the user story is not associated to a Jira issue, a new issue of the type mapped during the integration configuration will be created.
  • If the idea of the user story has an associated Jira issue, then the issue created for the user story will be linked to the idea issue.
  • If the idea doesn't have an associated Jira issue, then the user story will be created as a standalone issue unless the mapped issue type is a sub-task.
  • If the user story already has an associated Jira issue, then the Jira issue will be updated with the changes made in ProdPad. 
    
• Users are able to import Epics and User Story issue types as Ideas and User Stories.
  • The import is triggered from the import menu on the ideas list. You can access this menu by clicking the ellipsis tool (...) on the top right-hand side of the app followed by the Import From Jira button. 
  • The import is hard-coded to create Jira Epic Issues as Ideas and Jira Story Issues as User Stories. The integration uses the same field mapping as it does for pushing to Jira. 
  • The import will check to see if there is already an idea or story linked to the issue before creation. This reduces the chance of duplications being created, but if the ideas and stories aren't linked to issues in Jira, then there could be duplications made. 
    
• New issues created in Jira can be synced with ProdPad.
  • If the issue type of newly created issues in Jira Cloud and Server/Data Center projects matches ones mapped to either Ideas or User Stories in ProdPad, those newly created issues will be created in ProdPad as either Ideas or User Stories.
  • The user story will only be created in ProdPad if the parent ID of the issue in Jira Cloud and Server/Data Center projects is linked to an Idea in ProdPad.
  • The field mapping is the same as the mapping used for pushing to Jira.
• Sync Changes From Issues in Jira to ProdPad.
  • If a change is made to an issue in Jira that has an issue type mapped to Ideas or User Stories in ProdPad, those changes will update the linked Idea or Story within ProdPad. However, due to the nature of the sync, it can take up to 15 minutes for the changes to appear in the linked ideas or user stories in ProdPad. 
  • Any update made will overwrite what is in ProdPad. Once the Idea/Story is pushed, Jira Cloud becomes the source of truth. It's important to note here that if you're working on a pushed idea or user story in ProdPad, your work may be overwritten if the sync updates whilst you're updating the pushed idea or user story. 
  • Status changes made in Jira will be updated in ProdPad. 
  • The field mapping is the same as the mapping used for pushing to Jira. 

What are the current Jira Full Sync limitations?

The current Jira Full Sync integration limitations are:

• Currently, Jira Full Sync can only be used for mapping text fields. Required fields such as dates and selections (e.g. component, environment) are not currently handled. At the moment, the workaround for this limitation is to use the existing Jira Status Sync integration and make the fields not required, or set a default value on the field creation.
• Creating a custom hierarchy for issue types in Jira to be synced with ProdPad is currently not possible. 
• It is not possible to prevent mapping ideas to sub-tasks or user stories to epics, which might create issues with setting hierarchy during the issue creation.
• When importing issues into ProdPad, the workflow will check to see whether any issues already exist in ProdPad, but won't update any existing issues found. 
• Currently, attachments are not supported when pushing to Jira or importing to ProdPad.
• It is not possible for users to map multiple fields to multiple fields. Users can only map to a single field when creating a Jira Full Sync integration.
• Currently, personas, products, tags and attachments are not supported when pushing to Jira or importing to ProdPad.
• To stop the Jira full Sync integration, the integration will need to be deleted. To turn it back on, the integration will need to be remade.