---
title: "How to Use Basic Tasks to Extend Hierarchy Levels in BigPicture"
canonical: "https://support.appfire.com/space/SUPPORT/3707797515/How%20to%20Use%20Basic%20Tasks%20to%20Extend%20Hierarchy%20Levels%20in%20BigPicture"
format: markdown
---
# How to Use Basic Tasks to Extend Hierarchy Levels in BigPicture

This article covers two distinct use cases related to managing task structures and administrative tracking in BigPicture:

1. Using Basic Tasks to create additional hierarchy levels (e.g., between Epics and Tasks).
2. Identifying Box creators and managing Box creation permissions.

---

## Use Case 1: Creating Extra Hierarchy Levels with Basic Tasks

### Problem/Context

Users often want to extend the standard Jira hierarchy (Epic > Task > Sub-task) by adding intermediate levels, such as "Work Packages." Basic tasks are ideal for this because they exist only within BigPicture and do not sync back to Jira. However, users may encounter issues where they cannot indent or outdent Basic tasks into the desired position.

### Cause

This issue is typically caused by a conflict with **automated structure builders**. If a structure builder (like the Epic Link or Parent Link builder) is active and strictly enforces a rule (e.g., "Tasks must be direct children of Epics"), manually inserting a Basic task between them creates a structural conflict. BigPicture will block or revert the manual indentation to maintain the automated rule.

### Solution/Workaround

To use Basic tasks as an intermediate level (e.g., Epic > Basic Task > Jira Task):

1. **Identify the Conflicting Builder:** Go to **Box Configuration** > **Tasks** > **Task Structure**.
2. **Disable the Direct Parent Builder:** If you want to nest Basic tasks below an Epic, you must disable the builder that enforces the Epic-to-Task relationship (e.g., the Epic Link builder).
  - *Note:* Disabling a builder and re-enabling it will trigger a full structure rebuild.
3. **Manual Positioning:** Basic tasks do not have automated structure builders. Their position must be managed manually using drag-and-drop or the indent/outdent arrows in the Gantt or WBS view.
4. **Alternative Placement:** If you do not want to disable automated builders, keep the Basic task as a **sibling** of the Epic (at the same level) rather than an intermediate parent.

---

## Use Case 2: Tracking Box Creation and Managing Permissions

### Problem/Context

In environments where permissions are open ("Permissions for everyone"), it can be difficult to track who created specific Boxes, as there is no built-in audit log for Box creation.

### Solution/Workaround

#### Identifying the Creator

While there is no direct audit log, you can often identify the creator by checking the **Scope Owner**:

1. Navigate to **Box Configuration** > **Tasks** > **Scope definition**.
2. Check the **Scope Owner** field. The user listed here is almost always the person who initially set up the Box.

#### Restricting Future Box Creation

To prevent untracked Box creation and maintain better control:

1. Go to **App Administration** > **Security**.
2. Turn off the **"Permissions for everyone"** toggle.
3. Restrict permissions by assigning specific users the **Sub-box Creator** or **Box Admin** roles only on relevant parent or root boxes.

---

### Related Resources

- [Automatic Task Structure (Structure Builders)](https://support.appfire.com/space/SPM/1918536846/Automatic+task+structure+(structure+builders))
- [Basic Tasks / BigPicture Tasks](https://support.appfire.com/space/SPM/1918405930/Basic+tasks+%2F+BigPicture+tasks)
- [Box Security Roles](https://support.appfire.com/space/BPEdc/2533425825/Box+security+roles)