This page shows all non-archived structures available to you.
Name | Owner | Last opened | Applications | Manual adjustments | Access | Effectors | Actions |
---|---|---|---|---|---|---|---|
someone | 06/May/24 | View |
|
||||
someone | 06/May/24 | Control |
|
||||
someone | 12/Jan/24 | View |
|
||||
someone | View |
|
|||||
someone | 06/May/24 | View |
|
||||
This structure contains the tasks for the coming release, grouped by assignee. You can quickly see the unassigned tasks in the corresponding group and assign them to the users by drag-and-dropping them to the required group. In the Estimate totals column, you can see how much work each team member has for for this release. |
someone | 12/Jan/24 | View |
|
|||
This structure was built using automation: |
someone | 31/Aug/24 | View |
|
|||
someone | 11/Jun/24 | Control |
|
||||
This is the structure where John manages his tasks. You can see it inserted together with Mary's structure into Mary and John's Structure, where their team lead can track their work and add or reorder their tasks. |
someone | 07/Dec/23 | View |
|
|||
This structure shows how you can visualise links hierarchies in which you have child issues linked to several parents. |
someone | 31/Aug/24 | View |
|
|||
someone | 31/Aug/24 | View |
|
||||
This is the structure where Mary manages her tasks. You can see it inserted together with John's structure into Mary and John's Structure, where their team lead can track their work and add or reorder their tasks. |
someone | 25/May/23 | View |
|
|||
This is the structure where John's and Mary's structures are inserted. Now their team lead can track their work and add or reorder their tasks. |
someone | View |
|
||||
someone | 26/Oct/23 | View |
|
||||
someone | 11/Jun/24 | View |
|
||||
someone | 11/Jun/24 | View |
|
||||
someone | 12/Jan/24 | View |
|
||||
someone | 11/Jun/24 | View |
|
||||
This structure shows how the plugin can be used as a part of the SAFe implementation. The Themes and Program Kanban boards contain the Portfolio epics and Program epics that implement them. They are linked with the Implements link type. Team A and Team B scrum boards have the stories that the dev teams are working on and the epics form the Program board. The structure shows the full hierarchy across all these boards and allows to quickly modify links, epic links and rank as you move issues inside the structure, thus allowing you to work with multiple boards at the same time. |
someone | 06/May/24 | View |
|
|||
This structure contains several pages from the demo Confluence instance you can access at https://demo-structure3-wiki.almworks.com |
someone | 22/Dec/22 | View |
|
|||
someone | 11/Jun/24 | Control |
|
||||
someone | 22/Dec/22 | View |
|