--- title: "Use case: Build a task structure by versions" canonical: "https://support.appfire.com/space/SPM/2400714999/Use%20case%3A%20Build%20a%20task%20structure%20by%20versions" format: markdown --- > Macro (aura-html) ## Use case: Build a task structure by version (old navigation)
Expand | **Goal** | **Structure and visualize work within BigPicture according to Jira versions. **
Organize and manage project tasks by Jira versions in BigPicture and enable better release planning and visibility. | | --- | --- | | **Scenario** | A project manager manages a software product with multiple planned releases. To align work with these release timelines, they structure tasks by Jira versions in BigPicture. Each version represents a logical grouping of Jira issues assigned to a specific release. This allows for planning, visualizing, and monitoring progress per version. | | **Key benefits** | - **Release-focused planning **- organize tasks by Jira versions to match delivery schedules. - **Better visibility** - get a clear view of what’s included in each release and how tasks are progressing. - **Easy change management** - identify gaps within versions and adjust task assignments accordingly. | ## Preconditions [Role] You need at least a box admin role to manage the box configuration. [box] The box needs to be populated with a Jira space. [Jira versions] You need to have versions defined in Jira. You can’t create Jira versions directly in BigPicture. ## Build a task structure by versions step-by-step 1. Go to **box configuration **>** Tasks **>** Task structure**. 2. Select the **Release** option. 3. Click **Save**. 4. Once saved, projects and versions are added as task types on the **box configuration **>** Tasks **>** Scope definition** page. 5. The changes are immediately reflected on the Gantt chart. > ✅ **Tip:** > ✅ > ✅ - Click the **Key** link on the Gantt’s task list to be redirected to a selected version in Jira. > ✅ - You can move tasks between versions in BigPicture. All changes are instantly reflected in Jira. The video presents how to create a version-based task structure. ![Video presenting how to build task structure by versions.](media://e60fb0f5-4431-439c-804b-5b361d51da4b) ## Expected outcomes - Tasks are successfully organized by versions in BigPicture. - A project manager gains a clear view of planned work within each release version. - A project manager can monitor release progress, adjust plans, and move tasks between versions in BigPicture as needed. All changes are instantly reflected in Jira. ## Additional resources - Watch an overview video about the task structure in BigPicture. - Watch a video about the task structure based on components, versions, and sprints. - [https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918832018](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918832018)
## Use case: Build a task structure by version (new navigation)
Expand | **Goal** | **Structure and visualize work within BigPicture according to Jira versions. **
Organize and manage project tasks by Jira versions in BigPicture and enable better release planning and visibility. | | --- | --- | | **Scenario** | A project manager manages a software product with multiple planned releases. To align work with these release timelines, they structure tasks by Jira versions in BigPicture. Each version represents a logical grouping of Jira issues assigned to a specific release. This allows for planning, visualizing, and monitoring progress per version. | | **Key benefits** | - **Release-focused planning **- organize tasks by Jira versions to match delivery schedules. - **Better visibility** - get a clear view of what’s included in each release and how tasks are progressing. - **Easy change management** - identify gaps within versions and adjust task assignments accordingly. | ## Preconditions [Role] You need at least a box admin role to manage the box configuration. [box] The box needs to be populated with a Jira space. [Jira versions] You need to have versions defined in Jira. You can’t create Jira versions directly in BigPicture. ## Build a task structure by versions step-by-step 1. Go to **box configuration **>** Tasks **>** Task structure**. 2. Select the **Release** option. 3. Click **Save**. 4. Once saved, projects and versions are added as task types on the **box configuration **>** Tasks **>** Add work items from Jira **page. 5. The changes are immediately reflected on the Gantt chart. > ✅ **Tip:** > ✅ > ✅ - Click the **Key** link on the Gantt’s task list to be redirected to a selected version in Jira. > ✅ - You can move tasks between versions in BigPicture. All changes are instantly reflected in Jira. The video presents how to create a version-based task structure. ![Video presenting how to build task structure by versions.](media://e60fb0f5-4431-439c-804b-5b361d51da4b) ## Expected outcomes - Tasks are successfully organized by versions in BigPicture. - A project manager gains a clear view of planned work within each release version. - A project manager can monitor release progress, adjust plans, and move tasks between versions in BigPicture as needed. All changes are instantly reflected in Jira. ## Additional resources - Watch an overview video about the task structure in BigPicture. - Watch a video about the task structure based on components, versions, and sprints. - [https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918832018](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918832018)