[Structure for Jira] Pages FeedConfluence Syndication Feedhttps://wiki.almworks.com.2024-03-27_17-47-19__ImportExportViaSync v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199102621-22024-03-28T14:51:45Z2024-03-28T14:51:45Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-dc."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p> Import and Export are actually a one-time <a href="https://wiki.almworks.com/display/structure/Running+Resync">Resync</a>. Export is resync from Structure and import is resync into Structure. If you need to run export or import periodically, you can set up a synchronizer with all the parameters but without enabling it - so no synchronization happens in the background. When you need to export or import, you can open Synchronization Settings page for the structure and run Resync. Just make sure you've selected the correct Resync direction!</p></div></div>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.2024-03-27_17-47-19__ImportExportViaSync+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199102621&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:51:45Z.System Requirements v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199102193-22024-03-28T14:51:44Z2024-03-28T14:51:44Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-dc."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<h3 id="id-.SystemRequirementsv9.2-AtlassianPlatform">Atlassian Platform</h3><div class="table-wrap"><table class="wrapped confluenceTable"><colgroup><col/><col/></colgroup><tbody><tr><th class="confluenceTh">Jira Versions Supported</th><td class="confluenceTd"><p>8.20+ (by the latest version)</p><p>See also: <a class="external-link" href="https://confluence.atlassian.com/adminjiraserver071/supported-platforms-802592168.html">Platforms supported by Jira</a> </p></td></tr><tr><th class="confluenceTh">Jira Editions Supported</th><td class="confluenceTd"><p>Jira Core, Jira Software, Jira Service Management (formerly Jira Service Desk)</p></td></tr><tr><th colspan="1" class="confluenceTh">Jira Data Center</th><td colspan="1" class="confluenceTd"><p>Supported</p><p>See Server Requirements below</p></td></tr><tr><th colspan="1" class="confluenceTh">Confluence Versions <br/>(Structure.Pages) </th><td colspan="1" class="confluenceTd">7.4 – 8.3 + (by the latest version)</td></tr></tbody></table></div><h3 id="id-.SystemRequirementsv9.2-Databases">Databases</h3><p>Databases used by Jira are also supported by Structure. </p><h3 id="id-.SystemRequirementsv9.2-Browsers"><span style="color: rgb(0,0,0);">Browsers</span></h3><p>Structure Plugin is compatible with the following browsers:</p><div class="table-wrap"><table class="wrapped confluenceTable"><colgroup><col/><col/><col/></colgroup><tbody><tr><th class="confluenceTh"><p>Browser</p></th><th class="confluenceTh"><p>Supported versions</p></th><th class="confluenceTh"><p>Versions known to NOT work</p></th></tr><tr><td class="confluenceTd"><p>Mozilla Firefox</p></td><td class="confluenceTd"><p>All recent versions</p></td><td class="confluenceTd"><p> </p></td></tr><tr><td class="confluenceTd"><p>Chrome</p></td><td class="confluenceTd"><p>All recent versions</p></td><td class="confluenceTd"><p> </p></td></tr><tr><td class="confluenceTd"><p>Safari</p></td><td class="confluenceTd"><p>All recent versions on OS X</p></td><td class="confluenceTd"><p>Safari for Windows is not supported.</p></td></tr><tr><td class="confluenceTd"><p>Edge</p></td><td class="confluenceTd"><p>All recent versions</p></td><td class="confluenceTd"><p> Internet Explorer is not supported</p></td></tr><tr><td colspan="1" class="confluenceTd">Other browsers</td><td colspan="1" class="confluenceTd">Unsupported, but may work</td><td colspan="1" class="confluenceTd"> </td></tr></tbody></table></div><h3 id="id-.SystemRequirementsv9.2-ServerRequirements">Server Requirements</h3><ul><li>At least 100MB of free disk space is needed on the server. See <a href="https://wiki.almworks.com/display/structure/Structure+Files+Location">Structure Files Location</a> for details.<ul><li>On Jira Data Center, each node must have sufficient free disk space in the local home.</li></ul></li><li><p>Java process running Jira needs at least an additional 200 MB of heap memory. If running on Java 7 or earlier, ensuring sufficient free PermGen space is recommended. See <a href="https://wiki.almworks.com/display/structure/Memory+Guidelines">Memory Guidelines</a> for details. </p></li><li>Jira process must have read/write permissions to the Jira (local) home directory to create the <code>structure</code> sub-directory automatically.</li></ul><h3 id="id-.SystemRequirementsv9.2-Non-Conformingsystems">Non-Conforming systems</h3><p>With regards to systems that don't conform to Jira requirements and Structure requirements: while we sometimes know that a specific configuration doesn't work, more often it's a grey area so feel free to try and let us know the results.</p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.System+Requirements+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199102193&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:51:44Z.Sample Formulas - Historical Values v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199101854-22024-03-28T14:48:03Z2024-03-28T14:48:03Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-cloud."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<h3 class="p1" id="id-.SampleFormulas-HistoricalValuesv9.2-Showthehistoricalvalueofanissuefieldataspecificdate">Show the historical value of an issue field at a specific date</h3><p>In the example below, we're using the Due Date field. You can use any system or custom field.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Confluence" data-theme="Confluence">historical_value(this, "duedate", datetime("15/May/18 6:24 PM"))</pre>
</div></div><p class="p1"><em>Note: this formula also uses the Datetime function - <a class="unresolved" href="#">learn more</a></em></p><h3 id="id-.SampleFormulas-HistoricalValuesv9.2-Showthenumberoftasksaddedsincethelastsprintbegan">Show the number of tasks added since the last sprint began</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Confluence" data-theme="Confluence">SUM {
IF history.changes
.FILTER($.field = "sprint")
.LAST()
.changeGroup.timestamp > sprint.last().startDate: 1
}</pre>
</div></div><h3 class="p1" id="id-.SampleFormulas-HistoricalValuesv9.2-Showwhochangedthefieldvalue">Show who changed the field value</h3><p>The example below shows who changed the Resolution field, but you can replace "resolution" with another system or custom field:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Confluence" data-theme="Confluence">history.changes
.FILTER($.field = “resolution”).last().changeGroup.author</pre>
</div></div><h3 class="p1" id="id-.SampleFormulas-HistoricalValuesv9.2-TimeFlagged:Timethetaskwasmarkedwithaflag">Time Flagged: Time the task was marked with a flag </h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Confluence" data-theme="Confluence">with flag_change_time(value) =
history.changes
.filter($.field = "flagged")
.filter($.to = value)
.changeGroup.time :
with flag_on_time = flag_change_time("Impediment") :
with flag_off_time = flag_change_time("") :IF flag_on_time && flag_off_time : flag_off_time - flag_on_time
ELSE IF flag_on_time : now() - flag_on_time</pre>
</div></div><h3 class="p1 auto-cursor-target" id="id-.SampleFormulas-HistoricalValuesv9.2-Timeinstatusforaspecificmonth">Time in status for a specific month</h3><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
<pre class="syntaxhighlighter-pre" data-syntaxhighlighter-params="brush: java; gutter: false; theme: Confluence" data-theme="Confluence">WITH year = 2023:
WITH month = 1: // 1 for Jan, 12 for Dec
WITH keyStatus = "in progress": // key-insensitive
WITH calendar = "Standard work calendar 8/5": // other option is Standard calendar 24/7, the value is locale-dependant, also Gantt calendars are available
WITH startDate = MAKE_DATE(year, month, 1):
WITH finishDate = MIN(DATE_ADD(startDate, 1, "month"), NOW()):
WITH isStart(change) = change.from != keyStatus AND change.to = keyStatus:
WITH isFinish(change) = change.from = keyStatus AND change.to != keyStatus:
WITH intervalFits(start, finish)
= start >= startDate AND start <= finishDate
OR finish >= startDate AND finish <= finishDate
OR start < startDate AND finish > finishDate:
WITH statusChanges = history.changes
.FILTER($.field = "status" AND ($.isStart() OR $.isFinish())):
WITH times = MERGE_ARRAYS(
IF statusChanges.FIRST().isFinish(): MIN(startDate, statusChanges.FIRST().changeGroup.time),
statusChanges.changeGroup.time,
IF statusChanges.LAST().isStart(): MAX(finishDate, statusChanges.LAST().changeGroup.time)
):
IF times: SEQUENCE(0, times.SIZE() - 1)
.FILTER(MOD($, 2) == 0 AND intervalFits(times.GET($), times.GET($ + 1)))
.MAP(CALENDAR_DURATION(MAX(times.GET($), startDate), MIN(times.GET($ + 1), finishDate), calendar))
.SUM()</pre>
</div></div>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.Sample+Formulas+-+Historical+Values+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199101854&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:48:03Z.Copying a Structure v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199101416-32024-03-28T14:48:03Z2024-03-28T14:48:03Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-cloud."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p><p>With the <strong>Copy</strong> action, you can create a full copy of a structure, and, optionally, clone every issue in the structure.</p><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>If you need to copy only a part of a structure, create a new empty structure and use <a href="https://wiki.almworks.com/display/structure/Moving+Items+Between+Structures">Issue Clipboard</a> to copy a part of the structure.</p></div></div><h2 id="id-.CopyingaStructurev9.2-CreateaCopy">Create a Copy</h2><p>To create a copy of a structure, open the <a href="https://wiki.almworks.com/display/structure/Managing+Structures">Manage Structures</a> page using the top navigation <strong>Structure</strong> menu. Find the structure you'd like to copy and click the <strong>Copy</strong> link in the Operations column.</p><p class="auto-cursor-target"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="750" src="https://wiki.almworks.com/download/attachments/199101416/Copy%20Structure.png?version=1&modificationDate=1711562831000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199101416/Copy%20Structure.png?version=1&modificationDate=1711562831000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199101423" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Copy Structure.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199101416" data-linked-resource-container-version="3"></span></p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>If you don't see <strong>Copy</strong> in the Operations column, you probably <a href="https://wiki.almworks.com/display/structure/Changing+Permission+to+Create+New+Structures"><span class="inline-comment-marker">do not have permissions</span> </a>to create new structures.</p></div></div><p>The <strong>Copy Structure</strong> page will show you the information about the structure, including its size and the number of issues, <a href="https://wiki.almworks.com/display/structure/Types+of+Generators">generators</a>, and <a href="https://wiki.almworks.com/display/structure/Synchronization">synchronizers</a> it contains. If the structure contains <a href="https://wiki.almworks.com/display/structure/Automation">automation</a>, you can click the <strong>Calculate</strong> link in the <strong>Visible Content</strong> section to execute the generators and see the generated content statistics.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Copy settings" width="650" src="https://wiki.almworks.com/download/attachments/199101416/CleanShot%202021-07-22%20at%2021.24.47.jpeg?version=1&modificationDate=1711562831000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199101416/CleanShot%202021-07-22%20at%2021.24.47.jpeg?version=1&modificationDate=1711562831000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199101421" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="CleanShot 2021-07-22 at 21.24.47.jpeg" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/jpeg" data-linked-resource-container-id="199101416" data-linked-resource-container-version="3" title="Copy settings"></span></p><p>Select the following options for copying the structure:</p><ol><li><strong>Choose whether or not to include Quick Transformation and/or Notes column data.</strong></li><li><strong>Choose how to handle generators and generated content</strong>, if the structure has any:<ul><li>Copy generators to the resulting structure – the new structure will contain copies of the generators from the original structure, which will generate the same content. This is the default.</li><li>Replace all generators with the generated content – <span class="inline-comment-marker" data-ref="e47670aa-5352-4f64-8e51-7d749b233cde">the new structure will contain only the generated content (issues, folders, etc.) and not the generators themselves (so the content will not automatically update with Jira changes).</span></li><li>Do not copy generators – the new structure will contain only the non-automated content from the original structure. The generators and generated parts will not be copied.</li></ul></li><li><strong>Choose if you'd like to copy <a href="https://wiki.almworks.com/display/structure/Synchronization">synchronizers</a></strong>, if the structure has any. If you don't see a <strong>Copy Synchronizers</strong> option, either the structure does not have any synchronizers or you<a href="https://wiki.almworks.com/display/structure/Changing+Permission+to+Manage+Synchronizers"> <span class="inline-comment-marker">do not have </span><span class="inline-comment-marker">permission</span></a> to create synchronizers. See <a href="https://wiki.almworks.com/display/structure/Copying+Synchronizers">Copying Synchronizers</a> for more details.</li><li><strong>Choose if you'd like to clone issues</strong> (see <a href="https://wiki.almworks.com/display/structure/Copying+a+Structure#CopyingaStructure-copyorclone">Copy vs. Clone</a>). If yes, <a href="https://wiki.almworks.com/display/structure/Copying+Structure+and+Cloning+Issues">enter the additional parameters for the cloning process</a>.</li></ol><p>Once you've made you selections, press <strong>Copy Structure</strong> or <strong>Start Cloning</strong>.</p><h2 id="id-.CopyingaStructurev9.2-TheNewStructure">The New Structure</h2><p>The new structure is created with the following properties:</p><ul><li>Structure name is automatically set to "Copy of <em><old structure name></em> (<em><date of copy></em>)".</li><li>Structure description is copied.</li><li>View settings are copied.</li><li>You become the owner of the copied structure.</li><li>If you have <strong>Control</strong> access level to the original structure, permission rules are copied. Otherwise, permission rules for the new structure are empty (it is a private structure). To share the new structure, add <a href="https://wiki.almworks.com/display/structure/Structure+Permissions">permission rules</a>.</li></ul><p>You can immediately edit the new structure's properties on the screen with the copy result.</p><h2 id="id-.CopyingaStructurev9.2-copyorcloneCopyvs.Clone"><span class="confluence-anchor-link" id="id-.CopyingaStructurev9.2-copyorclone"></span>Copy vs. Clone</h2><p>When copying a structure, you can choose to have the new structure use the same issues as the original structure or clone the original issues (create copies). The following chart explains the differences:</p><div class="table-wrap"><table class="wrapped confluenceTable"><colgroup><col/><col/><col/></colgroup><tbody><tr><th class="confluenceTh"><p> </p></th><th class="confluenceTh"><p>Copy Structure</p></th><th class="confluenceTh"><p>Copy Structure & Clone Issues</p></th></tr><tr><td class="confluenceTd"><p>Selected answer for <strong>Clone Issues?</strong></p></td><td class="confluenceTd"><p><strong>No</strong></p></td><td class="confluenceTd"><p><strong>Yes</strong></p></td></tr><tr><td class="confluenceTd"><p>New structure created?</p></td><td class="confluenceTd"><p>Yes</p></td><td class="confluenceTd"><p>Yes</p></td></tr><tr><td class="confluenceTd"><p>New structure contains:</p></td><td class="confluenceTd"><p>same Jira issues as the original structure</p></td><td class="confluenceTd"><p>clones (copies) of the issues from original structure</p></td></tr><tr><td class="confluenceTd"><p>Quick?</p></td><td class="confluenceTd"><p>Yes</p></td><td class="confluenceTd"><p>No, a background process is launched to do issue cloning</p></td></tr><tr><td class="confluenceTd"><p>Permissions required:</p></td><td class="confluenceTd"><p><strong>View</strong> access to the original structure <br class="atl-forced-newline"/> <strong>Create Structure</strong> permission</p></td><td class="confluenceTd"><p><strong>View</strong> access to the original structure <br class="atl-forced-newline"/> <strong>Create Structure</strong> permission <br class="atl-forced-newline"/> <strong>Bulk Change</strong> global Jira permission <br class="atl-forced-newline"/> A number of project-level permissions</p></td></tr></tbody></table></div><p>For details about configuring and running cloning, see <a href="https://wiki.almworks.com/display/structure/Copying+Structure+and+Cloning+Issues">Copying Structure and Cloning Issues</a>.</p></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.Copying+a+Structure+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199101416&revisedVersion=3&originalVersion=2">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:48:03Z.Agile Hierarchy Preset v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199102502-22024-03-28T14:36:37Z2024-03-28T14:36:37Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-cloud."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p class="auto-cursor-target">The Agile Hierarchy preset allows you tovisualize any project (or multiple projects) in a traditional Agile hierarchy (Epics > Stories/Tasks > Sub-tasks).</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Structure with Agile Hierarchy Preset" width="800" src="https://wiki.almworks.com/download/attachments/199102502/Agile%20Hierarchy%20Automation%20-%20Structure%20with%20Multiple%20Projects.png?version=1&modificationDate=1711559124000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102502/Agile%20Hierarchy%20Automation%20-%20Structure%20with%20Multiple%20Projects.png?version=1&modificationDate=1711559124000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102504" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Agile Hierarchy Automation - Structure with Multiple Projects.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102502" data-linked-resource-container-version="2" title="Structure with Agile Hierarchy Preset"></span></p><p>The Agile Hierarchy preset works for both Company-managed and Team-managed projects, and it allows you to combine both types of projects into a single structure.</p><h2 id="id-.AgileHierarchyPresetv9.2-BuildaNewStructureUsingtheAgileHierarchyPreset">Build a New Structure Using the Agile Hierarchy Preset</h2><p>To build a new structure using the Agile Hierarchy preset, open the <strong>Add</strong> menu, select <strong>Preset</strong>, and choose<span> </span><strong>Agile Hierarchy</strong>.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="select the agile hierarchy preset" width="500" src="https://wiki.almworks.com/download/attachments/199102502/Preset%20menu.png?version=1&modificationDate=1711559124000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102502/Preset%20menu.png?version=1&modificationDate=1711559124000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102505" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Preset menu.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102502" data-linked-resource-container-version="2" title="select the agile hierarchy preset"></span></p><p>You can select which boards or projects you want to include in your hierarchy.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Configuring the Agile Hierarchy preset" width="650" src="https://wiki.almworks.com/download/attachments/199102502/Agile%20Hierarchy%20-%20Settings.png?version=1&modificationDate=1711559124000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102502/Agile%20Hierarchy%20-%20Settings.png?version=1&modificationDate=1711559124000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102506" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Agile Hierarchy - Settings.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102502" data-linked-resource-container-version="2" title="Configuring the Agile Hierarchy preset"></span></p><h3 id="id-.AgileHierarchyPresetv9.2-RunsAs">Runs As</h3><p>When a generator runs, it runs as the structure owner. This is important because the generator will have access to the same projects, issues, etc. as the user listed here – if they don’t have permission to view an issue, it won’t be added to the structure.</p><h3 id="id-.AgileHierarchyPresetv9.2-Source">Source</h3><p>Choose whether you want to pull the epics from boards or projects. Then add the boards or projects you want to include.</p><h3 id="id-.AgileHierarchyPresetv9.2-Placethegeneratoron">Place the generator on</h3><p>Select where the generators should be placed within the structure hierarchy. This will determine the location of your Agile hierarchy, as all your epics will be placed on the same level as the generators, and stories/tasks and sub-tasks will be placed beneath those accordingly.</p><p>You have three options:</p><ul><li><strong>Current level</strong> - The generators will be placed on the currently-selected level.</li><li><strong>Level below</strong> - The generators will be placed on the level below the currently-selected item.</li><li><strong>Top level</strong> - The generators will be placed at the top of the structure.</li></ul><p><br/></p><p>Once you click <strong>Create</strong>, Structure will add a series of generators to:</p><ul><li>Add the epics from the selected boards/projects (<a href="https://wiki.almworks.com/pages/viewpage.action?pageId=130882355">JQL/Text Insert</a> or <a href="https://wiki.almworks.com/display/structure/Agile+Board+Inserter">Agile Board Insert</a>)</li><li>Add stories or tasks under each epic (<a href="https://wiki.almworks.com/display/structure/Child+Issues+Extend+Generator">Child Issues Extend</a>)</li><li>Add sub-tasks beneath the stories and tasks (<a href="https://wiki.almworks.com/display/structure/Child+Issues+Extend+Generator">Child Issues Extend</a>)</li></ul><h2 id="id-.AgileHierarchyPresetv9.2-AddingtheAgileHierarchyPresettoanExistingStructure">Adding the Agile Hierarchy Preset to an Existing Structure</h2><p>The Agile Hierarchy preset can also be added to existing structures. In this case, in addition to creating an Agile hierarchy for all epics in the selected projects/boards, it will also extend existing epics, stories and tasks in the structure, provided they are in its scope (see <a href="https://wiki.almworks.com/display/structure/Generator+Scope">Generator Scope</a> for details).</p><p>It will not add epics to stories already in the structure or add stories to sub-tasks already in the structure.</p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.Agile+Hierarchy+Preset+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199102502&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:36:37Z.Status Overview Preset v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199102490-22024-03-28T14:36:37Z2024-03-28T14:36:37Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-cloud."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p class="auto-cursor-target">The Status Overview preset allows you to visualize any project (or multiple projects) organized by issue status.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Structure built with a Status Overview preset" width="850" src="https://wiki.almworks.com/download/attachments/199102490/Structure%20built%20from%20Status%20Overview%20Preset.png?version=1&modificationDate=1711558923000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102490/Structure%20built%20from%20Status%20Overview%20Preset.png?version=1&modificationDate=1711558923000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102492" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Structure built from Status Overview Preset.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102490" data-linked-resource-container-version="2" title="Structure built with a Status Overview preset"></span></p><p>The Status Overview preset works for both Company-managed and Team-managed projects, and it allows you to combine both types of projects into a single structure.</p><h2 id="id-.StatusOverviewPresetv9.2-BuildaNewStructureUsingtheStatusOverviewPreset">Build a New Structure Using the Status Overview Preset</h2><p>To build a new structure using the Status Overview preset, open the <strong>Add</strong> menu, select <strong>Preset</strong>, and choose<span> </span><strong>Status Overview</strong>.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Add Status Overview preset" width="500" src="https://wiki.almworks.com/download/attachments/199102490/Preset%20menu.png?version=1&modificationDate=1711558923000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102490/Preset%20menu.png?version=1&modificationDate=1711558923000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102493" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Preset menu.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102490" data-linked-resource-container-version="2" title="Add Status Overview preset"></span></p><p>You can select which projects, issue types, and statuses to include in your hierarchy.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Configuring the Status Overview preset" width="600" src="https://wiki.almworks.com/download/attachments/199102490/Status%20Overview%20Preset%20-%20Settings%20-%20Issues-Subtasks.png?version=1&modificationDate=1711558923000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102490/Status%20Overview%20Preset%20-%20Settings%20-%20Issues-Subtasks.png?version=1&modificationDate=1711558923000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102494" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Status Overview Preset - Settings - Issues-Subtasks.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102490" data-linked-resource-container-version="2" title="Configuring the Status Overview preset"></span></p><h3 id="id-.StatusOverviewPresetv9.2-RunsAs">Runs As</h3><p>When a generator runs, it runs as the structure owner. This is important because the generator will have access to the same projects, issues, etc. as the user listed here – if they don’t have permission to view an issue, it won’t be added to the structure.</p><h3 id="id-.StatusOverviewPresetv9.2-Projects">Projects</h3><p>Select which projects you want to include.</p><h3 id="id-.StatusOverviewPresetv9.2-IssueTypes">Issue Types</h3><p>Select the types of issues to add to the structure. The hierarchy will be constructed with these issues beneath their respective statuses.</p><h3 id="id-.StatusOverviewPresetv9.2-IncludeStatuses">Include Statuses</h3><p>Select which statuses should be included in the hierarchy. Only issues in these statues will be added to the structure.</p><h3 id="id-.StatusOverviewPresetv9.2-SynchronizeissueorderwithJira">Synchronize issue order with Jira </h3><p>If selected, issues will be sorted based on their Jira rank, and moving issues in the structure will update their rank.</p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">This option adds a <a class="unresolved" href="#">Rank Sort generator</a> with the "Moving items in the structure will update ranks" option selected.</div></div><h3 id="id-.StatusOverviewPresetv9.2-Placethegeneratoron">Place the generator on</h3><p>Select where the generators should be placed within the structure hierarchy. This will determine the location of your Status Overview hierarchy.</p><p>You have three options:</p><ul><li><strong>Current level</strong> - The generators will be placed on the currently-selected level.</li><li><strong>Level below</strong> - The generators will be placed on the level below the currently-selected item.</li><li><strong>Top level</strong> - The generators will be placed at the top of the structure.</li></ul><p><br/></p><p>Once you click <strong>Create</strong>, Structure will add a series of generators to:</p><ul><li>Add issues from the selected projects (<a href="https://wiki.almworks.com/pages/viewpage.action?pageId=130882355">JQL/Text Insert</a>)</li><li>Add sub-tasks beneath the stories and tasks (<a href="https://wiki.almworks.com/display/structure/Child+Issues+Extend+Generator">Child Issues Extend</a>)</li><li>Group issues by status (<a href="https://wiki.almworks.com/display/structure/Group+by+Field">Group by Field</a>)</li><li>Synchronize issue order with Jira (<a href="https://wiki.almworks.com/display/structure/Sort+by+Field+Generator">Sort by Field</a>)</li></ul><h2 id="id-.StatusOverviewPresetv9.2-AddingtheStatusOverviewPresettoanExistingStructure">Adding the Status Overview Preset to an Existing Structure</h2><p>The Status Overview preset can also be added to existing structures. In this case, in addition to creating the selected hierarchy for the selected projects, it will also group existing issues by status, provided they are in its scope (see <a href="https://wiki.almworks.com/display/structure/Generator+Scope">Generator Scope</a> for details).</p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.Status+Overview+Preset+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199102490&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:36:37Z.Multi-project Overview Preset v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199102496-22024-03-28T14:36:37Z2024-03-28T14:36:37Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-cloud."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p class="auto-cursor-target">The Multi-project Overview preset allows you to visualize multiple projects organized by project.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Structure built using the Multi-Project Overview preset" width="850" src="https://wiki.almworks.com/download/attachments/199102496/Structure%20built%20from%20multi-project%20preset.png?version=1&modificationDate=1711559056000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102496/Structure%20built%20from%20multi-project%20preset.png?version=1&modificationDate=1711559056000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102499" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Structure built from multi-project preset.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102496" data-linked-resource-container-version="2" title="Structure built using the Multi-Project Overview preset"></span></p><p>The Multi-project Overview preset works for both Company-managed and Team-managed projects, and it allows you to combine both types of projects into a single structure.</p><h2 id="id-.Multi-projectOverviewPresetv9.2-BuildaNewStructureUsingtheMulti-projectOverviewPreset">Build a New Structure Using the Multi-project Overview Preset</h2><p>To build a new structure using the Multi-project Overview preset, open the <strong>Add</strong> menu, select <strong>Preset</strong>, and choose<span> </span><strong>Multi-project Overview</strong>.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Add a multi-project overview preset" width="500" src="https://wiki.almworks.com/download/attachments/199102496/Preset%20menu.png?version=1&modificationDate=1711559056000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102496/Preset%20menu.png?version=1&modificationDate=1711559056000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102500" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Preset menu.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102496" data-linked-resource-container-version="2" title="Add a multi-project overview preset"></span></p><p>You can select which projects and issue types to include in your hierarchy.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Configuring the multi-project overview preset" width="600" src="https://wiki.almworks.com/download/attachments/199102496/Multi-Project%20Preset%20-%20Settings%20-%20Epics.png?version=1&modificationDate=1711559056000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102496/Multi-Project%20Preset%20-%20Settings%20-%20Epics.png?version=1&modificationDate=1711559056000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102498" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Multi-Project Preset - Settings - Epics.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102496" data-linked-resource-container-version="2" title="Configuring the multi-project overview preset"></span></p><h3 id="id-.Multi-projectOverviewPresetv9.2-RunsAs">Runs As</h3><p>When a generator runs, it runs as the structure owner. This is important because the generator will have access to the same projects, issues, etc. as the user listed here – if they don’t have permission to view an issue, it won’t be added to the structure.</p><h3 id="id-.Multi-projectOverviewPresetv9.2-Projects">Projects</h3><p>Select which projects you want to include.</p><h3 id="id-.Multi-projectOverviewPresetv9.2-IssueTypes">Issue Types</h3><p>Select the types of issues to add to the structure. The hierarchy will be constructed with these issues beneath their respective projects.</p><h3 id="id-.Multi-projectOverviewPresetv9.2-Placethegeneratoron">Place the generator on</h3><p>Select where the generators should be placed within the structure hierarchy. This will determine the location of your Multi-project Overview hierarchy.</p><p>You have three options:</p><ul><li><strong>Current level</strong> - The generators will be placed on the currently-selected level.</li><li><strong>Level below</strong> - The generators will be placed on the level below the currently-selected item.</li><li><strong>Top level</strong> - The generators will be placed at the top of the structure.</li></ul><p><br/></p><p>Once you click <strong>Create</strong>, Structure will add a series of generators to:</p><ul><li>Add issues from the selected projects (<a href="https://wiki.almworks.com/pages/viewpage.action?pageId=130882355">JQL/Text Insert</a>)</li><li>Add stories or tasks under each epic (<a href="https://wiki.almworks.com/display/structure/Child+Issues+Extend+Generator">Child Issues Extend</a>)</li><li>Add sub-tasks beneath the stories and tasks (<a href="https://wiki.almworks.com/display/structure/Child+Issues+Extend+Generator">Child Issues Extend</a>)</li><li>Group issues by project (<a href="https://wiki.almworks.com/display/structure/Group+by+Field">Group by Field</a>)</li></ul><h2 id="id-.Multi-projectOverviewPresetv9.2-AddingtheMulti-projectOverviewPresettoanExistingStructure">Adding the Multi-project Overview Preset to an Existing Structure</h2><p>The Multi-project Overview preset can also be added to existing structures. In this case, in addition to creating the selected hierarchy for the selected projects, it will also group existing issues by project, provided they are in its scope (see <a href="https://wiki.almworks.com/display/structure/Generator+Scope">Generator Scope</a> for details).</p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.Multi-project+Overview+Preset+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199102496&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:36:37Z.Top Down Generators to Identify Blockers Across Projects v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199102456-22024-03-28T14:36:36Z2024-03-28T14:36:36Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-cloud."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p>Structure allows you to visualize the relationships between issues across multiple projects, in as many layers of hierarchy as you need. Let's imagine you're trying to complete a set of epics, and you need to see which issues are holding you up. Obviously, you need to know which stories aren't finished yet - but you probably need to go further that. What issues are blocking those stories from getting done? And do those blockers have blockers of their own?</p><p>Let's take a look at how easy it is to visualize all of your blockers, across multiple projects, in a single structure. </p><h2 id="id-.TopDownGeneratorstoIdentifyBlockersAcrossProjectsv9.2-Step1:InsertEpics">Step 1: Insert Epics</h2><p>Starting with a brand new, blank structure (see <a href="https://wiki.almworks.com/display/structure/Creating+Your+First+Structure">Creating Your First Structure</a>), open the <strong>Add</strong> menu and select <strong>Insert</strong>.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Select Insert from the Add menu" width="800" src="https://wiki.almworks.com/download/attachments/199102456/Add%20Menu%20-%20Insert.png?version=1&modificationDate=1711375518000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102456/Add%20Menu%20-%20Insert.png?version=1&modificationDate=1711375518000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102473" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Add Menu - Insert.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102456" data-linked-resource-container-version="2" title="Select Insert from the Add menu"></span></p><p>This will display the Insert generator options. Select <strong>JQL Query</strong>.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="500" src="https://wiki.almworks.com/download/attachments/199102456/Insert%20generator%20options_cloud.png?version=1&modificationDate=1711375518000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102456/Insert%20generator%20options_cloud.png?version=1&modificationDate=1711375518000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102464" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Insert generator options_cloud.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102456" data-linked-resource-container-version="2"></span></p><p>For this example, we're going to add the epics from our "Learning Structure" project using a JQL search. </p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="600" src="https://wiki.almworks.com/download/attachments/199102456/New%20insert%20generator_cloud.png?version=1&modificationDate=1711375518000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102456/New%20insert%20generator_cloud.png?version=1&modificationDate=1711375518000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102463" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="New insert generator_cloud.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102456" data-linked-resource-container-version="2"></span></p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>When entering a JQL query, auto-complete will suggest fields, operators and values as you type. It will also check that the JQL query is valid:<p style="margin-left: 30.0px;"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image confluence-thumbnail" width="20" src="https://wiki.almworks.com/download/thumbnails/115290573/JQL%20correct.png?version=1&modificationDate=1624629283000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/115290573/JQL%20correct.png?version=1&modificationDate=1624629283000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="115290719" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="JQL correct.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="115290573" data-linked-resource-container-version="7"></span> a green checkmark icon will appear if the query is valid</p><p style="margin-left: 30.0px;"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image confluence-thumbnail" width="20" src="https://wiki.almworks.com/download/thumbnails/115290573/JQL%20Error.png?version=1&modificationDate=1624629298000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/115290573/JQL%20Error.png?version=1&modificationDate=1624629298000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="115290720" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="JQL Error.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="115290573" data-linked-resource-container-version="7"></span> a red exclamation icon will appear if the query is invalid</p></p><p>To learn more about JQL, see the Atlassian article on <a class="external-link" href="https://confluence.atlassian.com/jiracoreserver073/advanced-searching-861257209.html">Advanced Searching</a>.</p></div></div><p>Once you click <strong>Apply</strong>, the Inserter will pull all issues that match your query into your new structure.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Structure with inserted epics" width="800" src="https://wiki.almworks.com/download/attachments/199102456/Structure%20with%20Epics.png?version=1&modificationDate=1711375518000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102456/Structure%20with%20Epics.png?version=1&modificationDate=1711375518000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102467" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Structure with Epics.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102456" data-linked-resource-container-version="2" title="Structure with inserted epics"></span></p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Your generators are listed in red.</p><ul><li>To make changes to a generator, double-click it.</li><li>To delete a generator, highlight its row and click the delete icon (<strong>x</strong>) or delete key.</li></ul></div></div><h2 id="id-.TopDownGeneratorstoIdentifyBlockersAcrossProjectsv9.2-Step2:ExtendwithStoriesandTasks">Step 2: Extend with Stories and Tasks</h2><p>Now it's time to<strong> Extend</strong> our results to include Stories and Sub-tasks. Open the <strong>Add</strong> menu, select <strong>Extend</strong>, and then choose <strong>Child Issues</strong>.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="500" src="https://wiki.almworks.com/download/attachments/199102456/Child%20Issues%20extend%20generator.png?version=1&modificationDate=1711375639000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102456/Child%20Issues%20extend%20generator.png?version=1&modificationDate=1711375639000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102460" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Child Issues extend generator.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102456" data-linked-resource-container-version="2"></span></p><p>Under Add, select <strong>Issues under epics</strong>. Next, you'll be asked to select which levels you want the Extender applied to. Since our epics are all on the first level of our hierarchy, we'll choose <strong>from 1 to 1</strong>. To learn more about customizing levels, see <a href="https://wiki.almworks.com/display/structure/Generator+Scope">Generator Scope</a>.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Child issue extend generator settings" width="500" src="https://wiki.almworks.com/download/attachments/199102456/Levels%201%20to%201.png?version=1&modificationDate=1711375864000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102456/Levels%201%20to%201.png?version=1&modificationDate=1711375864000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102459" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Levels 1 to 1.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102456" data-linked-resource-container-version="2" title="Child issue extend generator settings"></span></p><p>After clicking apply, Structure will add any linked stories or tasks beneath the epics we added in the previous step.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Automated Structure with stories under epics" width="800" src="https://wiki.almworks.com/download/attachments/199102456/Structure%20with%20Epics%20and%20Stories.png?version=1&modificationDate=1711375518000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102456/Structure%20with%20Epics%20and%20Stories.png?version=1&modificationDate=1711375518000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102470" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Structure with Epics and Stories.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102456" data-linked-resource-container-version="2" title="Automated Structure with stories under epics"></span></p><h2 id="id-.TopDownGeneratorstoIdentifyBlockersAcrossProjectsv9.2-Step3:AddBlockerswiththeLinkedItemsExtender">Step 3: Add Blockers with the Linked Items Extender</h2><p>Now it's time to add our blockers. Open the <strong>Add</strong> menu, select <strong>Extend</strong>, and then choose <strong>Linked Items...</strong></p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="500" src="https://wiki.almworks.com/download/attachments/199102456/Extend%20Options.png?version=1&modificationDate=1711375908000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102456/Extend%20Options.png?version=1&modificationDate=1711375908000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102458" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Extend Options.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102456" data-linked-resource-container-version="2"></span></p><p>Since we want to see all blockers affecting our issues, we're going to set the Link Type to <strong>Blocks</strong>, Link Direction to <strong>parent issue is blocked by sub issue </strong>and leave Extend Levels <strong>from 1 to 5</strong> (see <a href="https://wiki.almworks.com/display/structure/Linked+Items+Extender">Linked Items Extender</a> to learn more about these options).</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Linked issues extender settings dialogue" width="500" src="https://wiki.almworks.com/download/attachments/199102456/Updated%20Settings%20-%20Link%20extender.png?version=1&modificationDate=1711375518000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102456/Updated%20Settings%20-%20Link%20extender.png?version=1&modificationDate=1711375518000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102471" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Updated Settings - Link extender.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102456" data-linked-resource-container-version="2" title="Linked issues extender settings dialogue"></span></p><p>Blockers will now appear beneath the issues already in our structure. Notice that some of these blockers are from different projects, and some of them have their own blockers as well. Now we can quickly spot which issues are holding up our project!</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Structure with epics, stories, and linked issues" width="800" src="https://wiki.almworks.com/download/attachments/199102456/Structure%20with%20Epics%20Stories%20and%20Blockers.png?version=1&modificationDate=1711375518000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102456/Structure%20with%20Epics%20Stories%20and%20Blockers.png?version=1&modificationDate=1711375518000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102472" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Structure with Epics Stories and Blockers.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102456" data-linked-resource-container-version="2" title="Structure with epics, stories, and linked issues"></span></p><h2 id="id-.TopDownGeneratorstoIdentifyBlockersAcrossProjectsv9.2-TakingitFurther">Taking it Further</h2><p>This is just one of many ways to build a top-down structure. Depending on your needs, you may want to:</p><ul><li>Include different types of links, or view different link types on different hierarchy levels.</li><li>Add sub-tasks - just select <strong>Sub-tasks</strong> when adding your Child Issue Extend generator.</li></ul><p>We don't have space to cover all those options in this guide, but you can explore your options in the <a href="https://wiki.almworks.com/display/structure/Automation">Automation</a> section of our User's Guide.</p><h2 id="id-.TopDownGeneratorstoIdentifyBlockersAcrossProjectsv9.2-NextSteps">Next Steps</h2><p>Next, we'll take a look at how to create a bottom-up structure, which can be very useful for tracking projects and tasks across teams or departments.</p><p><a href="https://wiki.almworks.com/display/structure/Bottom+Up+Generators+for+Backlog+Grooming">Bottom Up Generators for Backlog Grooming</a></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.Top+Down+Generators+to+Identify+Blockers+Across+Projects+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199102456&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:36:36Z.Scrum Backlog Preset v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199100610-22024-03-28T14:36:36Z2024-03-28T14:36:36Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-cloud."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p class="auto-cursor-target">The Scrum Backlog preset allows you to visualize any project (or multiple projects) organized by sprints.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Structure built with the Scrum Backlog preset" width="850" src="https://wiki.almworks.com/download/attachments/199100610/Structure%20built%20from%20Scrum%20Backlog%20Preset.png?version=1&modificationDate=1711557605000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199100610/Structure%20built%20from%20Scrum%20Backlog%20Preset.png?version=1&modificationDate=1711557605000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199100611" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Structure built from Scrum Backlog Preset.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199100610" data-linked-resource-container-version="2" title="Structure built with the Scrum Backlog preset"></span></p><p>The Scrum Backlog preset works for both Company-managed and Team-managed projects, and it allows you to combine both types of projects into a single structure.</p><h2 id="id-.ScrumBacklogPresetv9.2-BuildaNewStructureUsingtheScrumBacklogPreset">Build a New Structure Using the Scrum Backlog Preset</h2><p>To build a new structure using the Scrum Backlog preset, open the <strong>Add</strong> menu, select <strong>Preset</strong>, and choose <strong>Scrum Backlog</strong>.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="select the Scrum Backlog preset" width="500" src="https://wiki.almworks.com/download/attachments/199100610/Preset%20menu.png?version=1&modificationDate=1711557605000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199100610/Preset%20menu.png?version=1&modificationDate=1711557605000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199100612" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Preset menu.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199100610" data-linked-resource-container-version="2" title="select the Scrum Backlog preset"></span></p><p>You can select which boards/projects you want to include, how issues are grouped, and more.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Configuring the Scrum Backlog preset" width="600" src="https://wiki.almworks.com/download/attachments/199100610/Scrum%20Backlog%20Preset%20-%20Settings%20-%20Sprint-status.png?version=1&modificationDate=1711557605000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199100610/Scrum%20Backlog%20Preset%20-%20Settings%20-%20Sprint-status.png?version=1&modificationDate=1711557605000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199100613" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Scrum Backlog Preset - Settings - Sprint-status.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199100610" data-linked-resource-container-version="2" title="Configuring the Scrum Backlog preset"></span></p><h3 id="id-.ScrumBacklogPresetv9.2-RunsAs">Runs As</h3><p>When a generator runs, it runs as the structure owner. This is important because the generator will have access to the same projects, issues, etc. as the user listed here – if they don’t have permission to view an issue, it won’t be added to the structure.</p><h3 id="id-.ScrumBacklogPresetv9.2-Source">Source</h3><p>Choose whether you want to pull the epics from boards or projects. Then add the boards or projects you want to include.</p><h3 id="id-.ScrumBacklogPresetv9.2-Groupby">Group by</h3><p>Select how you want issues organized within the structure. In the example above, we've selected <strong>Sprint > Status</strong> - this means our hierarchy will be organized as follows:</p><ul><li><strong>Level 1:</strong> Sprints</li><li><strong>Level 2:</strong> Statuses</li><li><strong>Level 3:</strong> Issues</li><li><strong>Level 4:</strong> Subtasks (if "Show subtasks" is selected under Options)</li></ul><h3 id="id-.ScrumBacklogPresetv9.2-SynchronizeissueorderwithJira">Synchronize issue order with Jira </h3><p>If selected, issues will be sorted based on their Jira rank, and moving issues in the structure will update their rank.</p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">This option adds a <a class="unresolved" href="#">Rank Sort generator</a> with the "Moving items in the structure will update ranks" option selected.</div></div><h3 id="id-.ScrumBacklogPresetv9.2-Hideissuesfromclosedsprints">Hide issues from closed sprints</h3><p>If this option is selected, issues from closed sprints will be hidden from the structure.</p><h3 id="id-.ScrumBacklogPresetv9.2-Showsubtasks">Show subtasks</h3><p>If this option is selected, subtasks will be added to the hierarchy beneath their corresponding issues.</p><h3 id="id-.ScrumBacklogPresetv9.2-Placethegeneratoron">Place the generator on</h3><p>Select where the generators should be placed within the structure hierarchy. This will determine the location of your Scrum Backlog.</p><p>You have three options:</p><ul><li><strong>Current level</strong> - The generators will be placed on the currently-selected level.</li><li><strong>Level below</strong> - The generators will be placed on the level below the currently-selected item.</li><li><strong>Top level</strong> - The generators will be placed at the top of the structure.</li></ul><p><br/></p><p>Once you click <strong>Create</strong>, Structure will add a series of generators to:</p><ul><li>Add issues from each selected board/project (<a href="https://wiki.almworks.com/pages/viewpage.action?pageId=130882355">JQL/Text Insert</a> or <a href="https://wiki.almworks.com/display/structure/Agile+Board+Inserter">Agile Board Insert</a>)</li><li>Group issues by sprints and any other field selected in the "Group by" setting (<a href="https://wiki.almworks.com/display/structure/Group+by+Field">Group by Field</a>)</li><li>Add sub-tasks beneath the stories and tasks (<a href="https://wiki.almworks.com/display/structure/Child+Issues+Extend+Generator">Child Issues Extend</a>)</li><li>Synchronize issue order with Jira (<a href="https://wiki.almworks.com/display/structure/Sort+by+Field+Generator">Sort by Field</a>)</li></ul><h2 id="id-.ScrumBacklogPresetv9.2-AddingtheScrumBacklogPresettoanExistingStructure">Adding the Scrum Backlog Preset to an Existing Structure</h2><p>The Scrum Backlog preset can also be added to existing structures. In this case, in addition to creating the selected hierarchy for the selected boards/projects, it will also group existing issues by the items selected in the "Group by" setting, provided they are in its scope (see <a href="https://wiki.almworks.com/display/structure/Generator+Scope">Generator Scope</a> for details).</p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.Scrum+Backlog+Preset+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199100610&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:36:36Z.Bottom Up Generators for Backlog Grooming v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199102475-22024-03-28T14:36:36Z2024-03-28T14:36:36Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-cloud."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p>Now that you've seen how easy it is to track tasks across multiple projects using the Extend generator, let's look at how we can use the Group generator to look at work assigned to specific teams or team members – and quickly manage your backlog.</p><h2 id="id-.BottomUpGeneratorsforBacklogGroomingv9.2-Step1:InsertStories">Step 1: Insert Stories</h2><p>Just as with our <a href="https://wiki.almworks.com/display/structure/Top+Down+Generators+to+Identify+Blockers+Across+Projects">top-down structure</a>, we'll begin with a blank structure (see <a href="https://wiki.almworks.com/display/structure/Creating+Your+First+Structure">Creating Your First Structure</a>). Open the <strong>Add</strong> menu and select <strong>Insert</strong>. </p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Select Insert from the Add menu" width="800" src="https://wiki.almworks.com/download/attachments/199102475/Add%20Menu%20-%20Insert.png?version=1&modificationDate=1711376103000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102475/Add%20Menu%20-%20Insert.png?version=1&modificationDate=1711376103000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102479" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Add Menu - Insert.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102475" data-linked-resource-container-version="2" title="Select Insert from the Add menu"></span></p><p>This will display the Insert generator options. Select <strong>JQL Query</strong>.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="500" src="https://wiki.almworks.com/download/attachments/199102475/Insert%20generator%20options_cloud.png?version=1&modificationDate=1711376103000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102475/Insert%20generator%20options_cloud.png?version=1&modificationDate=1711376103000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102478" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Insert generator options_cloud.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102475" data-linked-resource-container-version="2"></span></p><p>This time, we'll use the JQL Query to specify the projects we want to include and add just the stories. </p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="600" src="https://wiki.almworks.com/download/attachments/199102475/New%20insert%20generator%20-%20stories_cloud.png?version=1&modificationDate=1711376103000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102475/New%20insert%20generator%20-%20stories_cloud.png?version=1&modificationDate=1711376103000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102477" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="New insert generator - stories_cloud.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102475" data-linked-resource-container-version="2"></span></p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>When entering a JQL query, auto-complete will suggest fields, operators and values as you type. It will also check that the JQL query is valid:<p style="margin-left: 30.0px;"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image confluence-thumbnail" width="20" src="https://wiki.almworks.com/download/thumbnails/115290573/JQL%20correct.png?version=1&modificationDate=1624629283000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/115290573/JQL%20correct.png?version=1&modificationDate=1624629283000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="115290719" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="JQL correct.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="115290573" data-linked-resource-container-version="7"></span> a green checkmark icon will appear if the query is valid</p><p style="margin-left: 30.0px;"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image confluence-thumbnail" width="20" src="https://wiki.almworks.com/download/thumbnails/115290573/JQL%20Error.png?version=1&modificationDate=1624629298000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/115290573/JQL%20Error.png?version=1&modificationDate=1624629298000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="115290720" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="JQL Error.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="115290573" data-linked-resource-container-version="7"></span> a red exclamation icon will appear if the query is invalid</p></p></div></div><p>The Insert generator will pull all issues that match our query into the new structure. In this case, they will add the stories from our specified project.</p><p><span style="color: rgb(255,0,0);"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Structure with stories inserted" width="850" src="https://wiki.almworks.com/download/attachments/199102475/Structure%20with%20Stories%20Inserted.png?version=1&modificationDate=1711376103000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102475/Structure%20with%20Stories%20Inserted.png?version=1&modificationDate=1711376103000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102482" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Structure with Stories Inserted.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102475" data-linked-resource-container-version="2" title="Structure with stories inserted"></span><br/></span></p><p>These will serve as the bottom-most level of our hierarchy, and we will use Groupers to add levels above this.</p><h2 id="id-.BottomUpGeneratorsforBacklogGroomingv9.2-Step2:GroupbySprint">Step 2: Group by Sprint</h2><p>Open the <strong>Add</strong> menu again, select <strong>Group</strong>, and then choose <strong>Field...</strong></p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Select Field on the Group menu" width="500" src="https://wiki.almworks.com/download/attachments/199102475/Group%20-%20select.png?version=1&modificationDate=1711376103000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102475/Group%20-%20select.png?version=1&modificationDate=1711376103000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102483" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Group - select.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102475" data-linked-resource-container-version="2" title="Select Field on the Group menu"></span></p><p>You can group items by most Jira fields. For now, select <strong>Sprint</strong> in the Field dropdown list and click <strong>Apply.</strong></p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Field Grouper settings - Group by Sprint" width="500" src="https://wiki.almworks.com/download/attachments/199102475/Updated%20Settings%20-%20Group%20by%20sprint.png?version=1&modificationDate=1711376103000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102475/Updated%20Settings%20-%20Group%20by%20sprint.png?version=1&modificationDate=1711376103000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102484" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Updated Settings - Group by sprint.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102475" data-linked-resource-container-version="2" title="Field Grouper settings - Group by Sprint"></span></p><p>At this point, all of your stories should appear beneath their respective sprints.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Structure with Stories grouped by sprint" width="850" src="https://wiki.almworks.com/download/attachments/199102475/Structure%20-%20Stories%20grouped%20by%20sprints.png?version=1&modificationDate=1711376103000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102475/Structure%20-%20Stories%20grouped%20by%20sprints.png?version=1&modificationDate=1711376103000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102485" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Structure - Stories grouped by sprints.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102475" data-linked-resource-container-version="2" title="Structure with Stories grouped by sprint"></span></p><p>Now we'll add another level to our hierarchy, so we can see who is doing the work for each sprint.</p><h2 id="id-.BottomUpGeneratorsforBacklogGroomingv9.2-Step3:GroupbyAssignee">Step 3: Group by Assignee</h2><p>Once again, open the <strong>Add</strong> menu, select <strong>Group</strong>, and then choose <strong>Field...</strong></p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Select Field on the Group menu" width="500" src="https://wiki.almworks.com/download/attachments/199102475/Group%20-%20select.png?version=1&modificationDate=1711376103000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102475/Group%20-%20select.png?version=1&modificationDate=1711376103000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102483" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Group - select.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102475" data-linked-resource-container-version="2" title="Select Field on the Group menu"></span></p><p>This time, group by <strong>Assignee</strong>.</p><p><span style="color: rgb(255,0,0);"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Field Grouper settings - Group by Assignee" width="500" src="https://wiki.almworks.com/download/attachments/199102475/Updated%20Settings%20-%20Group%20by%20assignee.png?version=1&modificationDate=1711376103000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102475/Updated%20Settings%20-%20Group%20by%20assignee.png?version=1&modificationDate=1711376103000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102486" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Updated Settings - Group by assignee.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102475" data-linked-resource-container-version="2" title="Field Grouper settings - Group by Assignee"></span><br/></span></p><p>Once you apply this new generator, the top-level of your hierarchy will show all of your sprints. Under each of these, you can see which team members are assigned to which stories.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Structure with stories grouped by sprint and assignee" width="850" src="https://wiki.almworks.com/download/attachments/199102475/Structure%20-%20Stories%20grouped%20by%20sprints%20and%20assignee.png?version=1&modificationDate=1711376103000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102475/Structure%20-%20Stories%20grouped%20by%20sprints%20and%20assignee.png?version=1&modificationDate=1711376103000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102487" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Structure - Stories grouped by sprints and assignee.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102475" data-linked-resource-container-version="2" title="Structure with stories grouped by sprint and assignee"></span></p><p>Any stories that have yet to be assigned will be placed under an <strong>Unassigned</strong> folder. </p><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body">If you need to group items in a different order (for example, you want the top level to show assignees, and under that sprints), simply rearrange the Groupers in your structure.</div></div><h2 id="id-.BottomUpGeneratorsforBacklogGroomingv9.2-TakingitFurther">Taking it Further</h2><p>It's easy to add or adjust elements of a structure built with generators. Here are a few examples:</p><ul><li>Perhaps you want to see who worked on which projects for a fix version. Simply add another Grouper, this time grouping by Fix Version.</li><li>Do you prefer to organize work by teams? Use a Team custom field instead of Assignee.</li><li>You can group by any other field you need to visualize.</li><li>Need to see sub-tasks under your stories? Use the <a href="https://wiki.almworks.com/display/structure/Child+Issues+Extend+Generator">Child Issues Extend generator</a> to add sub-tasks. </li></ul><p>There are hundreds of other possibilities, allowing you to create the perfect hierarchy for your business needs – or several perfect hierarchies! In this guide, we focused on building down with extenders and building up with groupers, but you don't have to work in just one direction. You can start in the middle and add both extenders and groupers.</p><p>To learn more, check out our full articles on <a href="https://wiki.almworks.com/display/structure/Automation">Automation</a>.</p><p><br/></p><h2 id="id-.BottomUpGeneratorsforBacklogGroomingv9.2-NextSteps">Next Steps</h2><p>If you're interested in learning about adding items to a structure manually, continue on to <a href="https://wiki.almworks.com/display/structure/Building+a+Structure+Manually">Building a Structure Manually</a></p><p>If you prefer to just stick with generators, jump ahead to <a href="https://wiki.almworks.com/display/structure/Editing+Issues+in+Structure">Editing Issues in Structure</a></p><p><br/></p><p><br/></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.Bottom+Up+Generators+for+Backlog+Grooming+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199102475&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:36:36Z.Track Overdue Tasks with Structure v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199102438-22024-03-28T14:36:35Z2024-03-28T14:36:35Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-cloud."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p>Use Structure to identify:</p><ol><li><span><span>Overdue tasks</span></span></li><li>Number of overdue tasks per epic, initiative, or other larger grouping</li><li><p>Ratio of overdue tasks to total tasks for each epic, initiative, or other large grouping</p></li></ol><h3 id="id-.TrackOverdueTaskswithStructurev9.2-Step1:BuildYourStructure">Step 1: Build Your Structure</h3><p><p>In this guide, we're going to show you how to track overdue tasks at the epic level. To track overdue tasks for initiatives or any other large groupings, simply reconfigure the structure hierarchy - this can be done using different <a href="https://wiki.almworks.com/display/structure/Insert+Generators">Insert</a>, <a href="https://wiki.almworks.com/display/structure/Extend+Generators">Extend</a>, and <a href="https://wiki.almworks.com/display/structure/Group+Generators">Group </a>generators.</p><p>To create a new structure:</p><ol><li>Go to the Jira menu and select <strong>Structure | Create Structure</strong></li><li>Add epics: <strong style="letter-spacing: 0.0px;">Automation | Insert | JQL Query </strong>and enter the following JQL query: <code style="letter-spacing: 0.0px;">issuetype = Epic</code><ul><li>To limit the epics to specific projects or other variables, add additional specifications (Example: <code>AND project = "My Epics"</code>)</li></ul></li><li>Add stories: <strong>Automation | Extend | Stories under Epics...</strong></li><li>Add sub-tasks (optional):<strong> Automation | Extend | Sub-tasks...</strong></li></ol><p><strong><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="800" src="https://wiki.almworks.com/download/attachments/199102438/Overdue%20tasks%20DC%20-%20hierarchy.png?version=1&modificationDate=1711375427000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102438/Overdue%20tasks%20DC%20-%20hierarchy.png?version=1&modificationDate=1711375427000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102452" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Overdue tasks DC - hierarchy.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102438" data-linked-resource-container-version="2"></span><br/></strong></p></p><h3 id="id-.TrackOverdueTaskswithStructurev9.2-Step2:MarkOverdueTasks">Step 2: Mark Overdue Tasks</h3><p>Once you have your structure in place, the next step is to identify all the overdue items. To do this, we need to add a <a href="https://wiki.almworks.com/display/structure/Formula+Column">formula column</a>. Click the <strong>+ </strong>button to the right of the column headers, and select <strong>Formula. </strong><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="350" src="https://wiki.almworks.com/download/attachments/199102438/Overdue%20Tasks%20DC%20-%20add%20column.png?version=1&modificationDate=1711375427000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102438/Overdue%20Tasks%20DC%20-%20add%20column.png?version=1&modificationDate=1711375427000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102450" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Overdue Tasks DC - add column.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102438" data-linked-resource-container-version="2"></span></p><span style="color: rgb(0,0,0);">Give the column an appropriate name and enter the following into the Formula section: </span><code><span style="color: rgb(51,51,51);">IF(</span><a class="external-link" href="https://nick.demo.almworks.com/secure/StructureBoard.jspa?s=6" style="letter-spacing: 0.0px;"><span style="color: rgb(51,51,51);">due_date</span></a><span style="color: rgb(51,51,51);"> < today(); "overdue")</span></code><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="500" src="https://wiki.almworks.com/download/attachments/199102438/Overdue%20Tasks%20DC%20-%20formula.png?version=1&modificationDate=1711375427000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102438/Overdue%20Tasks%20DC%20-%20formula.png?version=1&modificationDate=1711375427000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102451" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Overdue Tasks DC - formula.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102438" data-linked-resource-container-version="2"></span></p></p><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body">If you used "due_date" in your formula, the variable will automatically be mapped to the Due Date attribute. If you used another name for that variable (for example, “due”), you will need to define the variable by pointing it to the appropriate Due Date attribute.</div></div><h4 id="id-.TrackOverdueTaskswithStructurev9.2-Variations">Variations</h4><p><p><span style="color: rgb(51,51,51);">This is just one way to mark overdue items. You could also:</span></p><ul><li><span style="color: rgb(51,51,51);">Create a more visual warning that highlights not only overdue items, but also items coming due. You can read how to do this in <a href="https://wiki.almworks.com/display/structure/Wiki+Markup+in+Formula+Columns">Wiki Markup in Formula Columns</a>.</span></li><li><span style="color: rgb(51,51,51);">Create a formula that relies on another due date. For example, you may want to flag issues that aren't completed by the due date of their parent epic. In this case, change the formula to: </span><code><span style="color: rgb(51,51,51);">IF(</span><a class="external-link" href="https://nick.demo.almworks.com/secure/StructureBoard.jspa?s=6" style="letter-spacing: 0.0px;"><span style="color: rgb(51,51,51);">type</span></a><span style="color: rgb(51,51,51);"> = "Story" and</span><a class="external-link" href="https://nick.demo.almworks.com/secure/StructureBoard.jspa?s=6" style="letter-spacing: 0.0px;"><span style="color: rgb(51,51,51);"> </span><span style="color: rgb(51,51,51);">status</span></a><span style="color: rgb(51,51,51);"> != "Done" and parent{</span><a class="external-link" href="https://nick.demo.almworks.com/secure/StructureBoard.jspa?s=6" style="letter-spacing: 0.0px;"><span style="color: rgb(51,51,51);">due_date</span></a><span style="color: rgb(51,51,51);">} < today(); "overdue")</span></code></li><li>Aggregate overdue items for epics (we'll cover this next!)</li></ul></p><h3 id="id-.TrackOverdueTaskswithStructurev9.2-Step3:AggregateOverdueItemsforEpics,Initiatives,etc."><span style="color: rgb(0,0,0);">Step 3: Aggregate Overdue Items for Epics, Initiatives, etc.</span></h3><p><span style="color: rgb(0,0,0);">In the previous example we were simply returning the string “overdue”, but if we give that "overdue" flag a numeric value ("1"), we can use the Sum over sub-items option to aggregate those values up the hierarchy. To accomplish this:</span></p><ol><li><span style="color: rgb(0,0,0);">In place of the formula we created in step 1, enter the following:<code> IF</code></span><code><span style="color: rgb(51,51,51);">(</span><a class="external-link" href="https://nick.demo.almworks.com/secure/StructureBoard.jspa?s=6" style="letter-spacing: 0.0px;"><span style="color: rgb(51,51,51);">type</span></a><span style="color: rgb(51,51,51);"> = "Story" and</span><a class="external-link" href="https://nick.demo.almworks.com/secure/StructureBoard.jspa?s=6" style="letter-spacing: 0.0px;"><span style="color: rgb(51,51,51);"> </span><span style="color: rgb(51,51,51);">status</span></a><span style="color: rgb(51,51,51);"> != "Done" and</span><a class="external-link" href="https://nick.demo.almworks.com/secure/StructureBoard.jspa?s=6" style="letter-spacing: 0.0px;"><span style="color: rgb(51,51,51);"> </span><span style="color: rgb(51,51,51);">due_date</span></a><span style="color: rgb(51,51,51);"> < today(); 1)</span></code></li><li>Check the Sum over sub-items box</li></ol><p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="800" src="https://wiki.almworks.com/download/attachments/199102438/Overdue%20Tasks%20DC%20-%20overdue%20count.png?version=1&modificationDate=1711375427000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102438/Overdue%20Tasks%20DC%20-%20overdue%20count.png?version=1&modificationDate=1711375427000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102442" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Overdue Tasks DC - overdue count.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102438" data-linked-resource-container-version="2"></span></p>In this example, we limited our scope to only stories that are not yet "Done" - depending on your situation, you may want to adjust this to include other issue types, add additional qualifications, etc.<h3 id="id-.TrackOverdueTaskswithStructurev9.2-Step4:CalculatethePercentageofStoriesThatAreOverdue">Step 4: Calculate the Percentage of Stories That Are Overdue</h3><p>So far, we've just identified and counted our overdue stories. But this doesn't paint a complete picture. And epic with 1 overdue item out of 257 is very different from 1 out of 5! </p><p>To get a better understanding of how these overdue items relate to the big picture, next we're going to:</p><ul><li>Calculate total stories for each higher level in our hierarchy</li><li>Calculate the percentage of stories that are overdue for each higher level</li></ul><p><span style="color: rgb(0,0,0);">First, we need to create another Formula column, which we'll use to calculate our total stories. For this column:</span></p><ul><li><span style="color: rgb(0,0,0);">Enter the following formula: <code>IF(type = "Story"; 1)</code></span></li><li><span style="color: rgb(0,0,0);">Check the Sum over sub-item box</span></li></ul><p class="auto-cursor-target"><span style="color: rgb(0,0,0);"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="500" src="https://wiki.almworks.com/download/attachments/199102438/Overdue%20Tasks%20DC%20-%20total%20stories.png?version=1&modificationDate=1711375427000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102438/Overdue%20Tasks%20DC%20-%20total%20stories.png?version=1&modificationDate=1711375427000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102441" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Overdue Tasks DC - total stories.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102438" data-linked-resource-container-version="2"></span><br/></span></p><p><span style="color: rgb(0,0,0);">Next, we'll create a third formula column to compare our values from the first two. For this column:</span></p><ol><li><span style="color: rgb(0,0,0);">E</span><span style="color: rgb(0,0,0);">nter the formula: </span><code style="color: rgb(0,0,0);letter-spacing: 0.0px;"><span style="color: rgb(51,51,51);">IF(</span><a class="external-link" href="https://nick.demo.almworks.com/secure/StructureBoard.jspa?s=6"><span style="color: rgb(51,51,51);">total_stories</span></a><span style="color: rgb(51,51,51);">;</span><a class="external-link" href="https://nick.demo.almworks.com/secure/StructureBoard.jspa?s=6"><span style="color: rgb(51,51,51);"> </span><span style="color: rgb(51,51,51);">overdue</span></a><span style="color: rgb(51,51,51);"> /</span><a class="external-link" href="https://nick.demo.almworks.com/secure/StructureBoard.jspa?s=6"><span style="color: rgb(51,51,51);"> </span><span style="color: rgb(51,51,51);">total_stories</span></a><span style="color: rgb(51,51,51);">)</span></code></li><li><span style="color: rgb(51,51,51);">Map your "total_stories" and "overdue" variables to the appropriate columns we created above</span></li></ol><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="800" src="https://wiki.almworks.com/download/attachments/199102438/Overdue%20Tasks%20DC%20-%20percent.png?version=1&modificationDate=1711375427000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102438/Overdue%20Tasks%20DC%20-%20percent.png?version=1&modificationDate=1711375427000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102440" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Overdue Tasks DC - percent.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102438" data-linked-resource-container-version="2"></span></p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">For this formula, we wrapped the expression in an if statement so we wouldn't get a DIV/0 error on lines without a value for total stories.</div></div><p><span><span>At this point, you can keep all three columns in your structure (we recommend <a href="https://wiki.almworks.com/display/structure/Saving+and+Sharing+Views">saving them as a new view</a>), or get rid of one or both of your original columns - our Percent column will keep their original calculations, even if those columns are deleted or changed. (This also means if you make changes to the formulas used in the Overdue or Total Stories column, you'll need to re-select those columns in the Variables section of your Percent formula to apply those changes there.)</span></span></p></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.Track+Overdue+Tasks+with+Structure+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199102438&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:36:35Z.Release Management with Structure v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-194643473-22024-03-28T14:36:34Z2024-03-28T14:36:34Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-cloud."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p>With Structure, you can track all the issues for upcoming releases – even if they're from different projects – and visualize all the data you need to track on a single screen.</p><h3 id="id-.ReleaseManagementwithStructurev9.2-Step1:BuildaReleaseManagementStructure">Step 1: Build a Release Management Structure</h3><p><p>To create a structure for release management: </p><ol><li>Go to the Jira menu and select <strong>Structure | Create Structure</strong></li><li>Add the issues you want to track – you can add them manually or automatically using <strong>Automation | Insert</strong></li><li>Group issues by fix version: <strong>Automation | Group | type "Fix Version/s"</strong> <em>(</em><em>Tip: </em><em>If you use the same names in different projects, use <strong>"Version name..."</strong> instead.)</em></li><li>Open the Summary settings and select <strong>Show Sprint and Version attributes</strong></li></ol><h3 id="id-.ReleaseManagementwithStructurev9.2-"><strong><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image s-wp-dialog-img confluence-external-resource" src="https://docs.5.pocker.alm.works/s/-ujjliu/940001/1dlckms/8.3.0.2/_/download/resources/com.almworks.jira.structure:welcome/img/dialog_release_group.gif" data-image-src="https://docs.5.pocker.alm.works/s/-ujjliu/940001/1dlckms/8.3.0.2/_/download/resources/com.almworks.jira.structure:welcome/img/dialog_release_group.gif"></span></strong></h3></p><h3 id="id-.ReleaseManagementwithStructurev9.2-Step2:AddData">Step 2: Add Data</h3><p><p>Next, add the data you need to track by clicking the <strong style="font-size: 14.0px;letter-spacing: 0.0px;">+ </strong>button at the top-right corner of the structure. You can add as many columns as you need, including:<ul><li>Jira fields, such as status, assignee, sprint, or remaining estimate</li><li><a href="https://wiki.almworks.com/display/structure/Progress+Column">Progress</a> - track status based on issue progress, percent completion, or resolution</li><li><a href="https://wiki.almworks.com/display/structure/Tempo+Work+Logged">Tempo Work Logged</a> - track how long your team is spending on each issue</li><li><a class="external-link" href="https://almworks.com/structure/help/column/formula">Formulas</a> - create your own formulas to compare fields or create a visual report</li><li><p class="auto-cursor-target"><a href="https://wiki.almworks.com/display/structure/Time+in+Status+Column">Time in Status</a> - see how much time issues spend in a particular status</p></li><li><p class="auto-cursor-target"><a class="external-link" href="https://almworks.com/structure/help/column/last-comment">Last Comment</a> - view the latest comment for each issue</p></li></ul><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="300" src="https://wiki.almworks.com/download/attachments/172163792/Add%20Column.png?version=1&modificationDate=1682350520000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/172163792/Add%20Column.png?version=1&modificationDate=1682350520000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="172163793" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Add Column.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="172163792" data-linked-resource-container-version="6"></span></p><p>Once you've added your columns, you can aggregate the data up the structure. To do so, open the column you want to aggregate and select <strong>Sum over sub-items</strong>.</p></p><p><br/><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Looking to manage resources for your next project? <a class="external-link" href="https://hubs.la/Q02jV0SM0">Planner</a> makes it easy to plan resources and capacity for your team.</p></div></div><p><br/></p></p></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.Release+Management+with+Structure+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=194643473&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:36:34Z.Manage Epics and Stories v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199102419-22024-03-28T14:36:34Z2024-03-28T14:36:34Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-cloud."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p>With Structure, you can easily organize issues into an advanced Agile hierarchy (Epics > Issues > Sub-tasks) AND identify any issues that aren't attached to epics.</p><h3 id="id-.ManageEpicsandStoriesv9.2-Step1:CreateaNewStructure">Step 1: Create a New Structure</h3><p><ol><li>Go to the Jira menu and select <strong>Structure | Create Structure</strong></li><li>On the Template page, select <strong>Empty Structure</strong></li></ol></p><h3 id="id-.ManageEpicsandStoriesv9.2-Step2:AddTwoFolders">Step 2: Add Two Folders</h3><p>Open the <strong>+Add</strong> menu and select <strong>Folder</strong>. Add two folders, named:</p><ul><li>"Agile Hierarchy"</li><li>"Issues without Epics"</li></ul><p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="800" src="https://wiki.almworks.com/download/attachments/199102419/Agile%20hierarchy%20-%20two%20folders.png?version=1&modificationDate=1711374950000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102419/Agile%20hierarchy%20-%20two%20folders.png?version=1&modificationDate=1711374950000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102426" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Agile hierarchy - two folders.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102419" data-linked-resource-container-version="2"></span></p></p><h3 id="id-.ManageEpicsandStoriesv9.2-Step3:InsertEpics">Step 3: Insert Epics</h3><p><p>Select the Agile Hierarchy folder, so that its row is highlighted, and add a JQL Query Insert Generator:</p><ol><li>Go to <strong>Automation | Insert | JQL Query</strong></li><li>Enter the following JQL query: <code>issuetype = Epic</code><ul><li>To limit the epics to specific projects or other variables, add additional specifications (Example: <code>AND project = "My Epics"</code>)</li></ul></li><li>Click <strong>Create</strong></li></ol><p>All your epics should now be placed beneath the Agile Hierarchy folder.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="800" src="https://wiki.almworks.com/download/attachments/199102419/Agile%20hierarchy%20-%20add%20epics.png?version=1&modificationDate=1711374950000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102419/Agile%20hierarchy%20-%20add%20epics.png?version=1&modificationDate=1711374950000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102425" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Agile hierarchy - add epics.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102419" data-linked-resource-container-version="2"></span></p><br/></p><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body">If the epics did not appear beneath the Agile Hierarchy folder, your generator was probably placed at the top of the structure, instead of beneath the folder. Select the "Insert issues: issuetype = Epic" row and drag it to beneath the Agile Hierarchy folder (see the picture above).</div></div><h3 id="id-.ManageEpicsandStoriesv9.2-Step4:InsertIssuesandSub-tasks">Step 4: Insert Issues and Sub-tasks</h3><p><p>Make sure the Agile Hierarchy folder is still selected, return to the <strong>Automation </strong>menu, and add the following two generators:</p><ul><li><strong>Extend | Stories under Epics...</strong></li><li><strong>Extend | Sub-tasks...</strong></li></ul><p><strong><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="800" src="https://wiki.almworks.com/download/attachments/199102419/Agile%20hierarchy%20-%20tasks%20and%20sub-tasks.png?version=1&modificationDate=1711374950000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102419/Agile%20hierarchy%20-%20tasks%20and%20sub-tasks.png?version=1&modificationDate=1711374950000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102424" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Agile hierarchy - tasks and sub-tasks.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102419" data-linked-resource-container-version="2"></span><br/></strong></p></p><h3 id="id-.ManageEpicsandStoriesv9.2-Step5:InsertIssueswithoutEpics">Step 5: Insert Issues without Epics</h3><p><p>Next, we need to make sure we don't lose track of any issues that aren't linked to epics yet. That's what our second folder is for:</p><ol><li>Select the "Issues without Epics" folder</li><li>Go to <strong>Automation | Insert | JQL Query</strong></li><li>Enter the following JQL query: <code style="letter-spacing: 0.0px;">issuetype != Epic AND issuetype in standardIssueTypes() AND "Epic Link" is empty</code><ul><li>If you narrowed your query to specific projects, etc. for your epics, do the same here</li></ul></li><li>Click <strong style="letter-spacing: 0.0px;">Create</strong></li></ol><p>Any issues that are not assigned to epics should now appear beneath the second folder.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="800" src="https://wiki.almworks.com/download/attachments/199102419/Agile%20hierarchy%20-%20issues%20without%20epics.png?version=1&modificationDate=1711374950000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102419/Agile%20hierarchy%20-%20issues%20without%20epics.png?version=1&modificationDate=1711374950000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102423" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Agile hierarchy - issues without epics.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102419" data-linked-resource-container-version="2"></span></p></p><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body">If no issues appear under the Issues without Epics folder, make sure the Insert Generator is located in the right location - if not, drag the generator to beneath the Issues without Epics folder (see the picture above).</div></div><h3 id="id-.ManageEpicsandStoriesv9.2-Step6:AssignIssuestoEpics/ReassignIssues">Step 6: Assign Issues to Epics / Reassign Issues</h3><p>Now that you have all your issues organized and in one place, you can assign issues from the second folder to epics, or even reassign issues that already have epics.</p><h4 id="id-.ManageEpicsandStoriesv9.2-AssigningIssuestoEpics">Assigning Issues to Epics</h4><p>To assign issues in the second folder to an epic:</p><ul><li>Drag the issues to the epic you want to assigned them to.</li><li>While dragging, hold down the <strong>ctrl</strong> key - this copies the issue to the new location in the structure. Once the issue is copied to the new location, it should disappear from beneath the second folder (because now it's assigned to an epic). </li></ul><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>Don't worry: copying an item in Structure does not make a copy in Jira.</p></div></div><h4 id="id-.ManageEpicsandStoriesv9.2-ReassigningIssuestoNewEpics">Reassigning Issues to New Epics</h4><p>To reassign issues from one epic to another, simply drag them from beneath their current epic to the new epic.</p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.Manage+Epics+and+Stories+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199102419&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:36:34Z.SAFe (Scaled Agile Framework) with Structure v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199102415-22024-03-28T14:36:33Z2024-03-28T14:36:33Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-cloud."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p>Everyone uses the Scaled Agile Framework (SAFe) a bit differently, but Structure is highly customizable and easy to tailor to your specific SAFe needs.</p><h3 id="id-.SAFe(ScaledAgileFramework)withStructurev9.2-Step1:BuildaSAFeStructure">Step 1: Build a SAFe Structure</h3><p><p>To create a structure for SAFe: </p><ol><li>Go to the Jira menu and select <strong>Structure | Create Structure</strong></li><li>Add initiatives: <strong>Automation | Insert | JQL Query |</strong> enter the appropriate JQL, such as <code>"Project = 'project name' AND issuetype = initiative"</code></li><li>Add epics below initiatives: <strong>Automation | Extend | Linked Issues |</strong> choose the type and direction used to assign Epics to Initiatives, such as "Implements" or "parent is Implemented by sub-issue"</li><li>Add issues belonging to epics: <strong>Automation | Extend | Stories under Epics</strong></li><li>Add sub-tasks: <strong>Automation | Extend | Sub-tasks</strong></li><li>Sort by rank: <strong>Automation | Sort | type "Rank"</strong></li></ol></p><h3 id="id-.SAFe(ScaledAgileFramework)withStructurev9.2-Step2:AddData">Step 2: Add Data</h3><p><p>Next, add the data you need to track by clicking the <strong style="font-size: 14.0px;letter-spacing: 0.0px;">+ </strong>button at the top-right corner of the structure. You can add as many columns as you need, including:<ul><li>Jira fields, such as status, assignee, sprint, or remaining estimate</li><li><a href="https://wiki.almworks.com/display/structure/Progress+Column">Progress</a> - track status based on issue progress, percent completion, or resolution</li><li><a href="https://wiki.almworks.com/display/structure/Tempo+Work+Logged">Tempo Work Logged</a> - track how long your team is spending on each issue</li><li><a class="external-link" href="https://almworks.com/structure/help/column/formula">Formulas</a> - create your own formulas to compare fields or create a visual report</li><li><p class="auto-cursor-target"><a href="https://wiki.almworks.com/display/structure/Time+in+Status+Column">Time in Status</a> - see how much time issues spend in a particular status</p></li><li><p class="auto-cursor-target"><a class="external-link" href="https://almworks.com/structure/help/column/last-comment">Last Comment</a> - view the latest comment for each issue</p></li></ul><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" width="300" src="https://wiki.almworks.com/download/attachments/172163792/Add%20Column.png?version=1&modificationDate=1682350520000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/172163792/Add%20Column.png?version=1&modificationDate=1682350520000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="172163793" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Add Column.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="172163792" data-linked-resource-container-version="6"></span></p><p>Once you've added your columns, you can aggregate the data up the structure. To do so, open the column you want to aggregate and select <strong>Sum over sub-items</strong>.</p></p><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p><strong>Take SAFe management to the next level</strong></p><p>By adding <a class="external-link" href="https://alm.works/pages">Structure.Pages</a>, you can manage your Strategy documentation and linked issues all in one place.</p><p><a class="external-link" href="https://almworks.com/structure/help/how-to/safe">Learn More</a></p></div></div></p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.SAFe+%28Scaled+Agile+Framework%29+with+Structure+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199102415&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:36:33Z.Child Issues Extend Generator v9.2Jaramy Connerstag:wiki.almworks.com,2009:page-199102404-22024-03-28T14:36:33Z2024-03-28T14:36:33Z<div class="feed"> <p>
Page
<b>edited</b> by
<a href=" https://wiki.almworks.com/display/~jaramy
">Jaramy Conners</a>
- "This page was merged and replaced by version FUTURE-cloud."
</p>
<div style="border-top: 1px solid #ddd; border-bottom: 1px solid #ddd; padding: 10px;">
<p>The Child Issues Extend generator pulls in issues based on Jira's Parent field. Once you've placed parent items in your structure, the Child Issue Extend generator can add:</p><ul><li>Stories/tasks (and other standard issue types) under epics</li><li>Sub-tasks under stories/tasks</li><li>Jira Plans (Advanced Roadmaps) hierarchy (down to epics)</li></ul><p class="confluence-link"><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Structure with child issues extend generator" width="800" src="https://wiki.almworks.com/download/attachments/199102404/Structure%20with%20child%20issues%20extend%20generator.png?version=1&modificationDate=1711040587000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102404/Structure%20with%20child%20issues%20extend%20generator.png?version=1&modificationDate=1711040587000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102407" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Structure with child issues extend generator.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102404" data-linked-resource-container-version="2" title="Structure with child issues extend generator"></span></p><p class="confluence-link">In the example above, we used a <a href="https://wiki.almworks.com/display/structure/Basic+Insert">Basic Insert generator</a> to add our epics; then we used the Child Issues Extend generator to add our tasks beneath our epics and our sub-task beneath those.</p><div class="confluence-information-macro confluence-information-macro-tip"><span class="aui-icon aui-icon-small aui-iconfont-approve confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>The Child Issues Extend generator works with both team-managed and company-managed projects.</p></div></div><h2 id="id-.ChildIssuesExtendGeneratorv9.2-AddingaChildIssuesExtendGenerator">Adding a Child Issues Extend Generator</h2><p>Open the <strong>Add</strong> menu and select <strong>Extend</strong>.</p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Add an Extend generator" width="800" src="https://wiki.almworks.com/download/attachments/199102404/Add%20menu%20-%20extend.png?version=1&modificationDate=1711040505000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102404/Add%20menu%20-%20extend.png?version=1&modificationDate=1711040505000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102409" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Add menu - extend.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102404" data-linked-resource-container-version="2" title="Add an Extend generator"></span></p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size">This will display the Extend generator options. Select <strong>Child Issues</strong>.</span></p><p><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" height="250" src="https://wiki.almworks.com/download/attachments/199102404/Child%20Issues%20extend%20generator.png?version=1&modificationDate=1711038796000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102404/Child%20Issues%20extend%20generator.png?version=1&modificationDate=1711038796000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102413" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Child Issues extend generator.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102404" data-linked-resource-container-version="2"></span></p><h2 id="id-.ChildIssuesExtendGeneratorv9.2-ConfiguringtheGenerator">Configuring the Generator</h2><p>Each Child Issues Extend generator can be customized to create exactly the hierarchy you need.</p><p><strong><span class="confluence-embedded-file-wrapper confluence-embedded-manual-size"><img class="confluence-embedded-image" alt="Child Issue extend generator settings" width="450" src="https://wiki.almworks.com/download/attachments/199102404/Child%20issues%20extend%20settings.png?version=1&modificationDate=1711371002000&api=v2" data-image-src="https://wiki.almworks.com/download/attachments/199102404/Child%20issues%20extend%20settings.png?version=1&modificationDate=1711371002000&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="199102406" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="Child issues extend settings.png" data-base-url="https://wiki.almworks.com" data-linked-resource-content-type="image/png" data-linked-resource-container-id="199102404" data-linked-resource-container-version="2" title="Child Issue extend generator settings"></span><br/></strong></p><h3 id="id-.ChildIssuesExtendGeneratorv9.2-RunsAs"><strong>Runs As</strong></h3><p>When a generator runs, it runs as the structure owner. This is important because the generator will have access to the same projects, issues, etc. as the user listed here – if they don’t have permission to view an issue, it won’t be added to the structure.</p><h3 id="id-.ChildIssuesExtendGeneratorv9.2-Add">Add</h3><p>Select the type of issues you want to add:</p><ul><li><strong>Issues under epics</strong> - adds all standard issue types (stories, tasks, etc.) under their associated epics.</li><li><strong>Sub-tasks</strong> - adds sub-tasks under standard issue types.</li><li><strong>Jira Plans hierarchy</strong> - adds items under your higher-level issues, down to epics. For example, if you place initiatives in your structure, this will add their corresponding epics.</li></ul><h3 id="id-.ChildIssuesExtendGeneratorv9.2-Sub-taskTypes"><strong>Sub-task Types</strong></h3><p>(Only visible if <strong>Add sub-tasks</strong> is selected.) Allows you to specify which types of sub-tasks to add to your structure, based on your <a class="external-link" href="https://confluence.atlassian.com/adminjiracloud/configuring-sub-tasks-818578898.html">sub-task configuration</a> in Jira. To include all sub-tasks, use the default <strong>All available sub-task types</strong>.</p><h3 id="id-.ChildIssuesExtendGeneratorv9.2-MovinganiteminthestructurewillchangeitsparentissueinJira"><strong>Moving an item in the structure will change its parent issue in Jira</strong> </h3><p>If this option is checked, the the parent field will be updated if you move an issue from beneath one parent item to another.</p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>You can change up to 100 issues with a single move. If you need to update more than 100 issues, simply move them in chunks of 100 or fewer.</p><p>Please be aware that it may take up to several minutes to process all changes if 100 issues are moved at one time.</p></div></div><h3 id="id-.ChildIssuesExtendGeneratorv9.2-ExtendLevels"><strong>Extend Levels</strong></h3><p>Allows you to specify which levels in the hierarchy the extender should be applied to:</p><ul><li>Levels are based on the placement of the generator, where "Level 1" is the level the generator is located on, "Level 2" is the level beneath that, and so on.</li><li>Child issues will only be added for those parent issues within the selected range.</li></ul><h3 id="id-.ChildIssuesExtendGeneratorv9.2-Placethegeneratoron"><strong>Place the generator on</strong></h3><p>Select where the generator should be placed within the structure hierarchy. This location will be considered "Level 1" when applying the generator (see "Extend Levels" above).<p>You have three options:</p><ul><li><strong>Current level</strong> - The generator will be placed on the currently-selected level. </li><li><strong>Level below</strong> - The generator will be placed on the level below the currently-selected item.</li><li><strong>Top level</strong> - The generator will be placed at the top of the structure.</li></ul></p><div class="confluence-information-macro confluence-information-macro-information"><span class="aui-icon aui-icon-small aui-iconfont-info confluence-information-macro-icon"></span><div class="confluence-information-macro-body">If a level is grayed out, it means it is not possible to place the generator on that level.</div></div><p>See <a href="https://wiki.almworks.com/display/structure/Generator+Scope">Generator Scope</a> to learn more.</p>
</div>
<div style="padding: 10px 0;">
<a href="https://wiki.almworks.com/display/structure/.Child+Issues+Extend+Generator+v9.2">View Online</a>
·
<a href="https://wiki.almworks.com/pages/diffpagesbyversion.action?pageId=199102404&revisedVersion=2&originalVersion=1">View Changes Online</a>
</div>
</div>Jaramy Conners2024-03-28T14:36:33Z