GreenHopper is now called JIRA Agile. Learn more.

Skip to end of metadata
Go to start of metadata

(info) Note that this page only applies if you are using the Classic Boards (which are no longer being actively developed; read more).

 

 

The 'Synchronise' feature in JIRA Agile helps you to preserve the integrity of the versions/components hierarchy in your project by detecting and repairing missing versions/components in the project hierarchy. You can run the project synchronisation manually or configure it to automatically detect and fix problems via listeners, if you have the appropriate administrator permissions.

To synchronise versions/components for a project,

Icon

You must have the 'Administer Projects' permission for a particular project to synchronise versions/components.

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Select Agile > Classic in the top navigation bar. Then select Classic Planning Board from the drop-down below the project name.
  3. Click the Tools menu and click Synchronise from the dropdown. JIRA Agile will synchronise your project versions/components for your project and display a confirmation window.

 

To configure JIRA Agile to automatically synchronise versions/components,

Icon

You must have the 'JIRA Administrators' global permission to configure JIRA Agile to automatically synchronise versions/components.

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Select JIRA Administration from the top bar, then select Add-ons > JIRA Agile.
    OR, if you are using JIRA 6.0 or later, click the 'cog' icon in the top bar, select Add-ons, then scroll down the page to the JIRA Agile section.
  3. Select JIRA Agile Configuration.
  4. Check the Versions Synchroniser and Components Synchroniser checkboxes under the JIRA Agile Listeners and Services section. Your changes will be saved immediately, i.e. the next time a change occurs that breaks the version/component hierarchy, JIRA Agile will automatically repair the missing associations.

0 Comments