Message-ID: <368642451.15128.1711688967452.JavaMail.appbox@confluence> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_15127_1885241137.1711688967452" ------=_Part_15127_1885241137.1711688967452 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html JIRA Agile (GreenHopper) Synchronizer

JIRA Agile (GreenHopper) Synchronizer

JIRA Agile (GreenHopper) Synchronizer lets you synchronize the posi= tion of issues in the structure and on an Agile board (such as a Scrum or K= anban board) using Rank synchronization, and synchronize an Epic field with= the position of stories under epics in the structure.
JIRA Agile Synchronizer Parameters
Synchronize

Choose mode of operation (G= reenHopper/JIRA Agile 6.1+ only):

  • Use Agile Board configuration (this feature is available only with JIRA= Agile/Greenhopper 6.1+)
  • Use custom projects and fields configuration
  Agile Board mode (GreenHopper/JIRA Agile 6.1+ only) parameters:
Agile Board JIRA Agile board to synchronize wi= th. The issues matching Board query will be synchronized. The structu= re may contain other issues, they will not be affected. If Ranking is turne= d on by ORDER BY clause in the query, it can be used for synchronization.
Synchronize Epics= If checked, epics will be synchron= ized with JIRA Agile epics.
Synchronize Rank<= /td> If checked, and Ranking is enabled= for Agile Board, it will be synchronized with Structure.
  Custom issue set mode and Gree= nHopper 6.0 and earlier parameters:

Project

A project that JIRA Agile is used in. The str= ucture may contain issues from other projects, they will not be affected. <= br class=3D"atl-forced-newline"> GreenHopper 5.8 or later:= Multiple projects may be selected. The issues from all selected projects w= ill be synchronized using the same Global Rank field.

Rank Field

The field of type "Rank" (managed by JIRA Agi= le) that holds the rank (backlog order) for the selected Project. If you do= not wish to synchronize rank, select Don't synchronize.

Epic Field

The field holding the Epic that the story bel= ongs to.

  • If you use epics on the Scrum boards in GreenHopper 6.1 and up, select = "Scrum Board Epics" as the Epic field to synchronize them.
  • If you use the Classic Planning Board, pick the appropriate custom f= ield of type "Labels", which is typically named "Epic/Theme".

    The synchronizer allows to select an Epic/Theme field even if it is appl= icable only to some of the available issue types. When the synchronizer sho= uld set a value to an Epic/Theme field, it will not make a change if the fi= eld is not applicable to the issue type of the changed issue.

  • If you do not wish to synchronize Epics content, select Don't synch= ronize.

Epic Type

Relevant only if an Epic Field is selected. D= efines an issue type that is treated as Epic - typically named "Epic". All = issues placed under an issue of this type in the structure will be updated = to have Epic Field point to that issue.

Auto-add Subtasks

When turned on, sub-tasks will be automatical= ly added to the structure and forced to stay under their respective parent = issues. This works similarly to Sub-Tasks Synchronizer.

This synchronizer supports both Import and Export / Resync into/from Str= ucture (more about res= ync). Incremental synchronization watches both structure changes a= nd JIRA Agile's changes and applies the change to the other side.

CAREFUL! Please be careful when using this synchronizer= , especially when you add multiple issues to the Structure, as this may lea= d to massive updates in the Agile ranks without undo.

On Fix Versions=

Earlier GreenHopper versions relied on values in the Fix in Vers= ion/s field - if a version has been released, the issues assigned = to that version won't appear on the Classic GreenHopper boards. GreenHopper= synchronizer in Structure reflected that behavior and ignored such issues.=

With the introduction of new Boards (known initially as Rapid Boards, th= en as Agile Boards), this dependency on Fix Version field has become option= al. In some cases, Fix Version field is completely disabled and the teams u= se Agile Sprints. To address that, the JIRA Agile synchronizer no longer fi= lters issues by Fix Version, unless you're using an old GreenHopper version= .

JI= RA Agile Synchronizer Rules

Common Rules:

Sub-Tasks Synchronization:

Rank Synchronization:

Epic Synchronization:

How to Add Issues to Structure Sync'ed with JIRA Agile

When JIRA Agile synchronizer is enabled, it automatically updates Agile = order in background when any Structure change happens. So if you carelessly= add issues from the sync'ed project to the structure in some random order,= their ranks will be updated according to that order.

To add issues to the structure without breaking the existing backlog ord= er:

Syncing = Partial Orders

JIRA Agile's Board is flat (except for sub-tasks), and the Structure is = hierarchical - so it is not possible to precisely rearrange Structure = to have all issues come in the same order as they do on the Planning Board,= without changing issue parents or making the Structure also flat. 

Henceforth, the Structure syncs subsets of the issues in the hierarchy w= ith Agile Rank. For example, consider the following Structure:

A

 

 

B

 

C

D

 

 

E

 

F

It is not possible to rearrange the sub-issues so that they come in the = following order: B, E, C, F - although this is possible on the Planning Boa= rd. Instead, the structure will synchronize sub-sets of the issues in the S= tructure with JIRA Agile. The following sub-sets will be synchronized separ= ately:

In JIRA Agile version 6.1 and later, the Epics are treated by JIRA Agile= as a separate set of issues, different from Stories and other non-Epics. T= o accommodate this change, Structure updates the rank of issues also using = "partial order" approach, syncing Epics and non-Epics separately. This mean= s that, starting with JIRA Agile 6.1, if an Epic comes before a Story on th= e Structure Board, it is not required that they come in the same order on t= he Scrum Board.

------=_Part_15127_1885241137.1711688967452--