help.k15t.com Open in urlscan Pro
52.222.236.82  Public Scan

Form analysis
1 forms found in the DOM

GET /search.html

<form role="search" id="search-form-hdeby8qh8y" method="GET" action="/search.html" data-vp-id="vp-search-form" class="flex w-full justify-center">
  <div data-vp-component="search-bar" data-vp-variant="" class="vp-search-bar has-suggestions">
    <div class="vp-search-bar__input-container">
      <div data-vp-component="search-input" class="vp-search-input"><input role="combobox" aria-controls="suggestion-akuwguvupy" aria-expanded="false" aria-autocomplete="list" required="" type="search" autocomplete="off" aria-label="Search"
          class="vp-search-input__input">
        <div class="vp-search-input__slot"></div><button type="submit" aria-label="Submit" class="vp-search-input__submit vp-search-input__icon"><svg data-vp-id="magnifier-icon" data-vp-component="icon" xmlns="http://www.w3.org/2000/svg" width="20"
            height="20" viewBox="0 0 20 20" fill="none" aria-hidden="true">
            <path
              d="M8.99452 14.5C10.5121 14.5 11.809 13.9669 12.8854 12.9007C13.9618 11.8345 14.5 10.5361 14.5 9.00548C14.5 7.48794 13.9631 6.19097 12.8893 5.11458C11.8155 4.03819 10.519 3.5 9 3.5C7.46786 3.5 6.16816 4.0369 5.1009 5.11071C4.03363 6.18453 3.5 7.48096 3.5 9C3.5 10.5321 4.0331 11.8318 5.09929 12.8991C6.1655 13.9664 7.46391 14.5 8.99452 14.5ZM9 16C8.02913 16 7.11974 15.816 6.27185 15.4479C5.42395 15.0799 4.68056 14.5799 4.04167 13.9479C3.40278 13.316 2.90278 12.576 2.54167 11.728C2.18056 10.88 2 9.97053 2 8.99956C2 8.04152 2.18403 7.13542 2.55208 6.28125C2.92014 5.42708 3.41864 4.68387 4.04758 4.0516C4.67653 3.41935 5.41569 2.91935 6.26508 2.5516C7.11449 2.18387 8.02548 2 8.99806 2C9.95769 2 10.8646 2.18403 11.7188 2.55208C12.5729 2.92014 13.316 3.42014 13.9479 4.05208C14.5799 4.68403 15.0799 5.42612 15.4479 6.27835C15.816 7.13058 16 8.0381 16 9.00094C16 9.83365 15.8615 10.6213 15.5846 11.3638C15.3078 12.1062 14.9254 12.7836 14.4375 13.3958L18 16.9583L16.9375 18L13.375 14.4583C12.7668 14.9459 12.0939 15.3247 11.3564 15.5948C10.6188 15.8649 9.83333 16 9 16Z"
              fill="currentColor"></path>
          </svg></button>
      </div>
    </div>
  </div>
</form>

Text Content

Cookie Notice

We use cookies to create a secure and effective browsing experience for our
website visitors and to understand how you use our site (i.e. Google Analytics).
For more information:
Click Here

OkDon't track me
Skip to main content Show navigation

Migrating to Scroll Documents? Check out our revamped Scroll Apps Migration Hub
→

×
 * Go to homepage

 * Get Started with Scroll
 * Support
 * Help FAQ
 * Scroll Apps Migration Hub

Page variant
Cloud

Show search form
 * Basics
   
   * Get started
     
   * Key features
     
   * Sync info panel
     
 * Migrate to Jira Cloud
   
   * Migration Path
     
     * Behind firewall
       
     * Remote License Migration
       
     * Server to Cloud → Cloud to Cloud
       
     * Server to Server (with Backbone)→ Cloud to Server (with Backbone)
       
     * Server (with Backbone) to Server → Cloud to Server (with Backbone)
       
   * Cloud & Data Center Differences
     
   * Cloud Roadmap
     
   * Migration scripts
     
 * Example Use Cases
   
   * Bidirectional synchronization
     
   * Unidirectional synchronization
     
   * Synchronize one project with multiple others
     
   * Synchronize a private with a public project
     
   * Synchronize only certain issues
     
   * Cross Deployment Synchronization
     
     * Configure a Project Banner
       
   * Synchronize with approval-based configuration
     
   * Synchronize with Jira Service Management
     
     * Mirroring (same-level support)
       
     * 2nd Level Support (Jira Service Management to Jira Software)
       
     * 2nd Level Support (Jira Service Management to Jira Service Management)
       
     * Power Customer Support
       
   * Synchronize Jira Data Center with Jira Cloud
     
   * Migrate Jira Projects
     
 * Configuration
   
   * Create a Synchronization
     
     * Mode: Review vs Immediate
       
     * Review Mode
       
     * Set up a Webhook Cloud to DC Sync
       
   * Synchronization detail view
     
   * Issue Type Mappings
     
   * Field Mappings
     
     * Common Field Mapping Types
       
   * Comments
     
   * Attachments
     
   * Advanced Settings
     
   * Project Mapping
     
   * Connection
     
   * Fields (Default values)
     
   * Workflow Mappings
     
   * Configuring the synchronization user
     
   * Notifications
     
   * Synchronizations overview
     
 * How-tos
   
   * Import/export synchronization configurations
     
   * Limit the synchronized issues
     
   * Unlink paired issues
     
   * Restrict Backbone usage to certain user-groups
     
   * Set the Synchronized Issue as an Issue Link
     
   * Sync Not Supported Fields
     
   * Pair existing issues to be synchronized
     
   * Add a sync button
     
   * Migrate a Backbone synchronization to a new Backbone synchronization
     
   * JQL search by Backbone attributes
     
   * Clear Sync Info Panel after moving issues between projects
     
 * Troubleshooting
   
   * Trigger a resync
     
   * Fix common problems
     
     * General problem situations
       
       * All fields have English names although Jira is in a different language
         
       * Authentication with an external Jira fails
         
       * Sync info panel displays wrong synchronization name, and no link to
         partner project
         
       * Why are my existing issues not immediately synced after creating a
         synchronization?
         
       * Attachments are not synchronized
         
       * Recently created issue types, fields, etc. are not available when
         editing configuration
         
     * Issue specific problem situations
       
       * Admin or project admin permissions are required
         
       * Attachments got duplicated
         
       * Bad gateway
         
       * Cannot add or remove watcher
         
       * Cannot create new issue without mapped issue type
         
       * Cannot find transition
         
       * Cannot find transition id
         
       * Cannot perform transition
         
       * Component(s) not valid
         
       * Could not resolve value of Project Key
         
       * Custom Field Mapping Error
         
       * Email Hidden in profile
         
       * Fallback user does not exist
         
       * Field not on the Screen
         
       * Incoming Issue Error
         
       * Incoming Version Error
         
       * Invalid JQL Filter
         
       * Invalid regex syntax
         
       * Issue does not exist
         
       * Issues must be assigned
         
       * Issue type not configured
         
       * Epic is not accessible
         
       * Missing attachment permissions
         
       * Missing Issue
         
       * Missing issue type
         
       * Missing message
         
       * Missing parent Issue error
         
       * Missing required fields
         
       * No create version permissions
         
       * Incompatible message format
         
       * No project administration permissions
         
       * Option not valid
         
       * Outgoing Issue error
         
       * Outgoing Send Error
         
       * Outgoing Version Error
         
       * Priority not valid
         
       * Resolution cannot be chosen
         
       * Resolution can not be set
         
       * Resolution was not found
         
       * Resolution was not mapped
         
       * Security level name is not valid
         
       * Sprint does not exist
         
       * Template error
         
       * The requested board cannot be viewed
         
       * User does not exist
         
       * User not assignable
         
       * User was not mapped
         
       * Version(s) not valid
         
       * Attachment exceeds file size
         
       * Workflow operation not valid
         
   * Analyze and fix errors
     
 * Administration
   
   * Installation
     
   * Security Advisories
     
   * Disable Usage Tracking
     
   * Licensing
     
     * Remote License
       
   * Supported Jira versions
     
 * Reference
   
   * Field mapping reference
     
     * Component
       
     * Dates
       
     * Issue links
       
     * Kepler custom fields
       
     * Elements Connect (formerly nFeed): supported fields
       
     * Power Database Fields
       
     * Resolution
       
     * Scriptrunner: scripted fields
       
     * Security level
       
     * Synchronize sprints
       
     * Version
       
     * Watchers
       
     * User
       
   * REST API
     
     * Introduction
       
     * Connectors
       
     * Asynchronous Tasks
       
     * Draft actions
       
     * Integration/Synchronization actions
       
   * Synchronization behavior
     
     * How a synchronization behaves when restarted after being down
       
     * How concurrent edits are handled
       
     * Issue history – how it's handled
       
     * Order of issue synchronization of issue changes
       
     * Synchronizing projects already containing issues
       
     * Deleting a Synchronized Issue
       
     * Deleting a Backbone Synchronization
       
     * Uninstalling Backbone
       
     * Errors that are retried automatically
       
     * Behavior of moving synced issues to another project
       
   * Glossary
     
   * Knowledge Base
     
     * Add a 'sync issue' button to the view issue screen
       
     * Configure only changes made by one synchronization partner to be
       synchronized
       
     * Basic Authentication Change Notice
       
     * Username Deprecation Notice
       
     * Clear the sync info panel
       
     * Change integration user to atlassian account
       
   * Support for team-managed projects
     
   * Jira Automation vs Backbone Issue Sync
     
   * Data Encryption
     
   * Handling Personal Data
     
 * Data Security and Performance
   
   * Certification
     
     * Is Backbone ISO certified?
       
     * Is Backbone GDPR compliant?
       
   * Data Security
     
     * How does Backbone ensure Cloud protection?
       
     * How does Backbone ensure data encryption?
       
     * How does Backbone use the Jira REST API?
       
     * Who can make changes to the Backbone configurations?
       
     * How does Backbone deal with security vulnerabilities?
       
     * Does Backbone notify customers in case of security breaches?
       
     * Do you have a list of your latest security advisories?
       
   * Data Handling
     
     * Does Backbone offer data residency?
       
     * How does Backbone handle personal data?
       
     * What info is exchanged between instances?
       
     * What info is stored by Backbone?
       
     * Where is my data hosted?
       
     * How long are the application logs stored?
       
     * Who can access my data?
       
     * How can I back up my data and where is it stored?
       
     * Is Backbone a data processor?
       
     * Does Backbone use any sub-processors when transferring data?
       
     * Does Backbone have a diagram illustrating where and how the data is
       stored and processed?
       
   * Data Residency
     
     * FAQ about Data Residency
       
     * How Does Data Residency Work in Backbone?
       
   * Performance
     
     * How long does it take for Backbone to sync a particular number of issues?
       
     * Can Backbone be used by enterprises and to sync a large number of issues?
       
     * How is a syncing error caused by Backbone detected and fixed?
       
     * Is there a limit to how many issues can be synced when migrating to Jira
       Cloud?
       
   * Configuration Modes
     
     * What different types of connections are possible using Backbone?
       
     * Can I synchronize a Jira instance from behind an enterprise firewall?
       
 * FAQs
   
   * Do you plan to synchronize with other systems?
     
   * Can I have the same issue keys in both projects?
     

 1. Backbone Issue Sync /
 2. Basics


Skip table of contents


GET STARTED




Thanks for choosing Backbone Issue Sync for Jira. Backbone helps you simplify
collaboration on projects, internally or across organizations, by synchronizing
Jira issues in real-time.

This guide will illustrate the steps required to get started with Backbone on
Jira Cloud.

Watch the video

To learn more about what Backbone can do for you, watch the Get Started video
that introduces Backbone’s features. 






1: FINDING BACKBONE IN JIRA

After installing Backbone Issue Sync for Jira from the Atlassian Marketplace,
you can find Backbone in the Jira sidebar of a project under the “Apps” tab.








To create your first project synchronization, follow these steps:

 1. Go to Project settings > Apps > Issue Synchronization.

 2. Click New Synchronization.

As illustrated below, Backbone allows you to create a synchronization:

 * With another project in the same instance.

 * With another Cloud instance.

 * With another DC instance.






2: SYNCHRONIZING PROJECTS USING BACKBONE

There are two separate sections in this guide.

 1. Synchronizing projects on the same Jira instance.

 2. Synchronizing projects on a separate Jira Cloud instance.

Syncing Projects on the Same Jira Instance


STARTING THE SYNCHRONIZATION





 1. Select the first option Synchronize with another project on this instance >
    Next.

 2. You will be prompted to select the project from the list of Jira projects
    available on your instance.
    For our example, we will create a synchronization between Project A and
    Project B. Choose the project to be synced.
    

 3. The name and description of the synchronization is already filled out. You
    have the option to change it as well.

 4. Click Send Request.


ACCEPTING THE SYNC REQUEST





Navigate to the relevant Jira project (Project B in this example).

 1. Go to the Project Settings > Apps > Issue Synchronization.
    
    1. Here you should see an Incoming Request message under Status in the
       Backbone panel.
       

 2. Click on the three dot menu (…) under Actions > View request.

 3. Click Accept Request > Start Configuration.
    
    
    Congratulations! The connection between Project A and Project B is
    established. You are now ready to start the configuration of your
    synchronization.

Syncing Projects on a Separate Jira Instance

This section will show you how to configure Backbone to synchronize issues
between projects across two separate Jira instances (referred to as instance A
and instance B).

Please make sure that you have installed Backbone on both Jira instances.

On instance A, create a new project called Project A, and on instance B, create
a new project called Project B.


STARTING THE SYNCHRONIZATION





Let's establish a connection between the two projects so they can communicate
with each other.

We'll send a 'Synchronization request' to the other instance. This request has
to be accepted by a Jira administrator or a project admin on the other instance
to establish the connection.

 1. Click New Synchronization.

 2. Select the second option Synchronize with another Cloud instance > Next.

 3. Select the second option Immediate > Next

 4. You will be prompted to enter the Base URL and Project Key in the Partner
    Instance column.
    
    1. In the Base URL field, enter the base URL of the Jira instance you want
       to synchronize with. The URL will have this
       structure: https://example.atlassian.net.
    
    2. In the Project Key field, you can enter a specific project key of a
       project on the partner instance. Enter Project B's project key and
       click Next.
       

 5. You can change the name and description of the synchronization. For now,
    let's stick with the default name and description and click Next.

 6. Check the configuration settings and click Send Request.


ACCEPTING THE SYNC REQUEST





Any user with the project admin status for project B on Instance B can accept
the synchronization request to establish the connection between the projects.

 1. Navigate to the relevant Jira project (Project B in this example).
    
    1. Go to the Project Settings > Apps > Issue Synchronization.
    
    2. Here you should see an Incoming Request message under Status in the
       Backbone panel.

 2. Click on the three dot menu (…) under Actions > View request.

 3. Click Accept Request > Start Configuration.


Congratulations! The connection between Project A and Project B is established.
You are now ready to start the configuration of your synchronization.





3: CONFIGURE SYNCHRONIZATION SETTINGS





After establishing a connection between two Jira projects, you can now select
the exact type of Jira data you want to synchronize. The following steps will
guide you on how to successfully set up a sync.

Issue Type Mapping:

 1. To start editing the synchronization, click Edit Configuration.

 2. Open the Issue Types tab and click Start with simple mappings.

 3. Select the issue types you want to map across Project A and Project B.
    a. In this example, we will select the issue type Task.

 4. You can use the drop down box and choose to synchronize the issue types
    either in both directions between Project A and Project B or in one
    direction.

 5. Click Create to save the issue type mapping.

Field Mapping:

 1. Navigate to the Fields - Mappings tab > + Field Mapping.
 2. Select the fields you want to synchronize. In this example, we will select
    Summary and Description.
 3. You can use the drop down box to synchronize issue fields either in one or
    both directions.
 4. Click Create to save the fields configuration.

Comments Mapping:

 1. Navigate to the Comments tab.

 2. Use the drop down box to choose between uni-directional or bi-directional
    comment mapping.

 3. Click Enriched mapping to get the complete information about the reporter
    and comment date and time.

 4. Click Publish Draft > Start Synchronization.

Well done! You've configured your first Backbone synchronization. Now, all
issues with type Task will be synchronized between Projects A and B.

The fields Summary and Description fields will be synchronized between those
issues along with any comments.


4: USING THE SYNCHRONIZATION





Now for the fun part: let's use Backbone to test the synchronization by creating
an issue type Task in Project B and testing whether the issue is automatically
synchronized to Project A.

 1. Create a new issue with type Task in Project B, and enter some text in
    the Summary and Description fields.

 2. Open Project A. You can see that the issue has now been synchronized.

 3. Open the synchronized issue in Project A and add a comment.

 4. Go back to the issue in Project B and open the synced Task. The comment can
    now be seen as well.

Easy-peasy! You have successfully created and tested your first synchronization.



Next steps:

Now, you can try out more configuration options, such as different issue/field
types, or comments and attachments.




×

Privacy Statement / Customer Agreement / Legal Notice / K15t Website /
Accessibility Statement
 * Copyright © 2024 K15t
 * • Powered by Scroll Viewport & Atlassian Confluence
 * 


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close