{"id":287,"date":"2026-02-19T12:19:51","date_gmt":"2026-02-19T20:19:51","guid":{"rendered":"https:\/\/deepplanner.io\/documentation\/?post_type=lsvr_kba&p=287"},"modified":"2026-02-19T12:19:52","modified_gmt":"2026-02-19T20:19:52","slug":"synchronizing-with-jira","status":"publish","type":"lsvr_kba","link":"https:\/\/deepplanner.io\/documentation\/knowledge-base\/synchronizing-with-jira\/","title":{"rendered":"Synchronizing with JIRA"},"content":{"rendered":"\n

In Deep Planner, it is possible to import or export epics from JIRA or establish an automatic synchronization. This article explains these features in detail.<\/p>\n\n\n\n

Import Epics From JIRA<\/h3>\n\n\n\n

It is possible to import work with type \u201cEpic\u201c from JIRA. In order to do this, go to Epics \u279dImport\/Export, then select the \u201cImport\u201c radiobutton and the \u201cAtlassian\u201c connection. Choose the cloud and JQL query to import. (For more information about JQL, refer to the JIRA documentation<\/a> on this topic.) Click the \u201cQuery\u201c button. This will display the list of JIRA epics available for import.<\/p>\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure><\/div>\n\n\n

Choose the epics that you want to import and click \u201cImport Selected Tickets.\u201c This will trigger the following behavior:<\/p>\n\n\n\n

    \n
  • Epics that already exist in Deep Planner will be updated with the most recent information from JIRA.<\/li>\n\n\n\n
  • Epics that do not exist in Deep Planner will be created with all information taken from JIRA.<\/li>\n<\/ul>\n\n\n\n

    When importing epics, the system will consume the following epic data from JIRA:<\/p>\n\n\n\n

      \n
    1. Name<\/strong><\/li>\n\n\n\n
    2. Description<\/strong><\/li>\n\n\n\n
    3. Status<\/strong><\/li>\n\n\n\n
    4. Dependencies<\/strong>\n
        \n
      1. Dependencies are imported based on Links with types \u201cis blocked by\u201c and \u201cblocks.\u201c<\/li>\n<\/ol>\n<\/li>\n\n\n\n
      2. High-Level Estimate<\/strong>\n
          \n
        1. The high-level estimate will only be imported if it is a newly imported epic or never modified on the Deep Planner side after the initial import.<\/li>\n\n\n\n
        2. If space is configured to use man-days, the estimate must be specified in the Original Estimate field in JIRA.<\/li>\n\n\n\n
        3. If space is configured to use story points, the estimate must be specified in the Story point estimate field in JIRA, with a custom name or the built-in field name, \u201cStory point estimate.\u201c<\/li>\n\n\n\n
        4. The timeline must be enabled and be displayed in JIRA epics for successful estimates import.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n\n\n\n

          Export Epics To JIRA<\/h3>\n\n\n\n

          It is possible to export Deep Planner epics to JIRA. In order to do this, go to Epics\u279dImport\/Export, then select the \u201cExport\u201c radiobutton and the \u201cAtlassian\u201c connection. Choose the cloud and project to export to. After selection, the system will show the list of Deep Planner epics available for export and their export parameters. Choose the required epics and their export parameters, then click \u201cExport Selected Epics\u201c to trigger the export.<\/p>\n\n\n\n

            \n
          • Epics that already exist in JIRA and were previously imported to Deep Planner to the current space will be updated with the most recent information from Deep Planner<\/li>\n\n\n\n
          • Epics that do not exist in JIRA or have no association with the current space will be created with all information taken from JIRA<\/li>\n<\/ul>\n\n\n\n

            When exporting epics, the system will update the following fields in JIRA:<\/p>\n\n\n\n

              \n
            1. Description:<\/strong>\n
                \n
              1. For description text, the system will take data from the Description field in the Deep Planner epic and copy it to JIRA.<\/li>\n\n\n\n
              2. In addition to the description itself, the system will also generate a section, \u201cGenerated by Deep Planner,\u201c and will add it to the JIRA epic description. The section will contain useful metadata. Depending on the selection in the export parameters, the system may export high-level estimates and user stories and link them to corresponding Deep Planner epic.<\/li>\n<\/ol>\n<\/li>\n\n\n\n
              3. Status:<\/strong> if \u201cInclude Status\u201d export parameter is enabled<\/li>\n\n\n\n
              4. Labels:<\/strong> The system will only modify labels that were explicitly defined in Deep Planner and assigned to teams. If \u201cInclude Teams as Labels\u201c is enabled, it will remove the team labels that were unassigned to a particular epic and add the team labels that were assigned in a roadmap schedule.<\/li>\n\n\n\n
              5. Start date:<\/strong> If \u201cInclude Start Date\u201c is enabled, the system will update it with \u201cStart date\u201c value from epic schedule,<\/li>\n\n\n\n
              6. Due date:<\/strong> If \u201cInclude End Date\u201c is enabled, the system will update it with \u201cEnd date\u201c value from epic schedule<\/li>\n\n\n\n
              7. Dependencies:<\/strong> for dependent epics the system will create \u201cis blocked by\u201c links<\/li>\n\n\n\n
              8. Original Estimate or Story point estimate<\/strong>\n
                  \n
                1. The estimate will only be exported if it is enabled in the export parameter, \u201cUpdate Original Estimate field.\u201d<\/li>\n\n\n\n
                2. If space is configured to use man-days, the estimate will be specified in the Original Estimate field in JIRA.<\/li>\n\n\n\n
                3. If space is configured to use story points, the estimate will be specified in the Story point estimate field in JIRA with a custom name or the built-in field name, \u201cStory point estimate.\u201c<\/li>\n\n\n\n
                4. The timeline must be enabled and displayed in JIRA epics for a successful estimate export.<\/li>\n\n\n\n
                5. If the export parameter is enabled and the fields are not properly configured in JIRA, the export may fail with an error.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n\n\n\n

                  Automatic Synchronization<\/h3>\n\n\n\n

                  It is possible to configure an automatic synchronization to import and export data from\/to JIRA automatically on regular intervals. To setup, go to \u201cSettings,\u201d click \u201cEdit,\u201c and then refer to the \u201cIntegrations\u201c tab. Select \u201cEnable automatic synchronization.\u201c Select the synchronization interval and export parameters. Click \u201cSave.\u201c<\/p>\n\n\n

                  \n
                  \"\"<\/figure><\/div>\n\n\n

                  Data Precedence Notice<\/h4>\n\n\n\n

                  If both JIRA and Deep Planner tickets were updated during the synchronization, the system will select the Deep Planner changes as a priority.<\/p>\n\n\n\n

                  Synchronization interval<\/h4>\n\n\n\n

                  This parameter is used to define how frequently the system synchronizes the JIRA and Deep Planner epics. The system will pull only tickets that were created or modified after the latest synchronization time. If changes were made in JIRA, the system will update Deep Planner tickets with the latest changes from JIRA. (Read the \u201cImport Epics from JIRA\u201c section for the list of fields that will be updated.) If changes were made in Deep Planner, the system will update JIRA tickets with the latest changes from Deep Planner. (Read the \u201cExport Epics to JIRA\u201c section for the list of fields that will be updated)<\/p>\n\n\n\n

                  Export Parameters <\/h4>\n\n\n\n

                  Export parameters are used in case the system needs to export Deep Planner changes to JIRA. See the \u201cExport Epics To JIRA\u201c section for more information about parameters.<\/p>\n\n\n\n

                  Export New Epics<\/h4>\n\n\n\n

                  It is possible to configure the system to create new epics in JIRA whenever a new epic is created in Deep Planner. To enable that, check \u201cExport Epics Created in Deep Planner\u201c and select the cloud and project into which the new epics will be exported<\/p>\n\n\n\n

                  Import New Epics<\/h4>\n\n\n\n

                  Deep Planner right now does not import new epics from JIRA automatically. To initiate an import, manually refer to the \u201cImport Epics From JIRA\u201c section.<\/p>\n\n\n\n

                  Synchronization Logs<\/h4>\n\n\n\n

                  Synchronization logs can help troubleshoot potential synchronization issues or impacts. To observe the logs, click \u201cBrowse Synchronization Logs,\u201d then select the start and end times to pull logs.<\/p>\n","protected":false},"excerpt":{"rendered":"

                  In Deep Planner, it is possible to import or export epics from JIRA or establish an automatic synchronization. This article explains these features in detail. Import Epics From JIRA It is possible to import work with type \u201cEpic\u201c from JIRA. In order to do this, go to Epics \u279dImport\/Export, then select the \u201cImport\u201c radiobutton and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"lsvr_kba_cat":[6],"lsvr_kba_tag":[],"class_list":["post-287","lsvr_kba","type-lsvr_kba","status-publish","format-standard","hentry","lsvr_kba_cat-general"],"_links":{"self":[{"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba\/287","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba"}],"about":[{"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/types\/lsvr_kba"}],"author":[{"embeddable":true,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/comments?post=287"}],"version-history":[{"count":1,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba\/287\/revisions"}],"predecessor-version":[{"id":290,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba\/287\/revisions\/290"}],"wp:attachment":[{"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/media?parent=287"}],"wp:term":[{"taxonomy":"lsvr_kba_cat","embeddable":true,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba_cat?post=287"},{"taxonomy":"lsvr_kba_tag","embeddable":true,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba_tag?post=287"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}