Message-ID: <1067300029.16002.1711713614865.JavaMail.appbox@confluence> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_16001_65363451.1711713614865" ------=_Part_16001_65363451.1711713614865 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
GreenHopper Synchronizer lets you synchronize the position of is= sues in the structure and on a GreenHopper board (such as a Scrum or Kanban= board, or the Classic Planning Board) using Rank synchronization, and sync= hronize an Epic field with the position of stories under epics in the struc= ture.
=20GreenHopper 5.8 introduced Global Rank field, which can be used= to manage a multi-project backlog. GreenHopper synchronizer in Structure l= ets you select multiple projects to sync with when you are using Global Ran= k.
Project | =20
A project that GreenHopper is used in. The s=
tructure may contain issues from other projects, they will not be affected.=
| =20
Auto-add Subtasks | =
=20
When turned on, sub-tasks will be automatica= lly added to the structure and forced to stay under their respective parent= issues, like they do on GreenHopper's Planning Board. This works similarly= to =EF=BB=BFSub= -Tasks Synchronizer. | =20
Rank Field | =20
The field of type "GreenHopper Rank" that ho= lds the rank (backlog order) for the selected Project. If you do not wish t= o synchronize rank, select Don't synchronize. | =20
Epic Field | =20
The field holding the Epic that the story be= longs to. =20
| =20
Epic Type | =20
Relevant only if an Epic Field is selected. = Defines 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. | =20
This synchronizer supports both Import and Export / Resync into/from Str= ucture (more about res= ync). Incremental synchronization watches both structure changes a= nd GreenHopper changes and applies the change to the other side.
=20CAREFUL! Please be careful when using this synchronize= r, especially when you add multiple issues to the Structure, as this may le= ad to massive updates in the GreenHopper ranks without undo.
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.=
=20With the introduction of new Boards (known for some time as Rapid Boards= ), this dependency on Fix Version field has become optional. In some cases,= Fix Version field is completely disabled and the teams use GreenHopper Spr= ints. To address that, the GreenHopper synchronizer no longer filters issue= s by Fix Version, unless you're using an old GreenHopper version.
=20Common Rules:
=20Sub-Tasks Synchronization:
=20Rank Synchronization:
=20This restricts the possible rank changes in GreenHopper - you can only m= ove an issue to the position of another issue that is under the same parent= issue in the structure, otherwise the issue will "jump back" later.
Epic Synchronization:
=20When GreenHopper synchronizer is enabled, it automatically updates Green= Hopper order in background when any Structure change happens. So if you car= elessly add issues from the sync'ed project to the structure in some random= order, their ranks will be updated according to that order.
=20To add issues to the structure without breaking the existing backlog ord= er:
=20GreenHopper's Planning Board is flat (except for sub-tasks), and the Str= ucture is hierarchical - so it is not possible to =EF=BB=BFprecisely r= earrange 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.
=20Henceforth, the Structure syncs subsets of the issues in the hierarchy w= ith GreenHopper rank. For example, consider the following Structure:
=20A | =20
| =20
| =20
B | =20
| =20
C | =20
D | =20
| =20
| =20
E | =20
| =20
F | =20
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 GreenHopper. The following sub-sets will be synchronized sepa= rately:
=20In GreenHopper version 6.1 and later, the Epics are treated by GreenHopp= er as a separate set of issues, different from Stories and other non-Epics.= To accommodate this change, Structure updates the rank of issues also usin= g "partial order" approach, syncing Epics and non-Epics separately. This me= ans that, starting with GreenHopper 6.1, if an Epic comes before a Story on= the Structure Board, it is not required that they come in the same order o= n the Scrum Board.