How does the hierarchy of Task Issue Types work in Profit.co?

Profit.co provides an option to classify tasks using different Issue Types such as Epics, Stories, Tasks, Sub-tasks, and Bugs.

Why this feature?

• Efficient planning and tracking: Large initiatives can be broken down into smaller parts, making it easier to assign owners, set timelines, and monitor progress without losing sight of the bigger picture.
• Clear structure for teamwork: By defining whether an item is an Epic, Story, Task, Sub-task, or Bug, teams know exactly where the work fits in the overall plan. 
• Better prioritization: Different types of work require different attention -  for example, Bugs often need urgent fixes, while Epics may span multiple sprints. Categorizing items helps teams focus on what matters most at the right time.
• Flexibility as work evolves: If the scope changes, tasks can be converted from one type to another (e.g., turning a Task into a Story if it grows in complexity), ensuring that the structure always matches the reality of execution.
• Transparency & accountability: With clear types and hierarchy, managers and team members can see dependencies, track ownership, and ensure accountability at every level of work.

Step 1:

Navigate to Settings → Tasks from the left navigation panel and switch to the Issue Types tab. Enable the Issue Types toggle on the Issue Type page. 

Note: Only Superusers can enable or disable the Issue Type via Settings.

After that, navigate to Tasks → Workspace from the left navigation panel. And create a new Workspace. 

On the create workspace side panel, enable the Issue Type toggle.

Step 2:

After creating the Workspace, proceed to create a Board. From the Board Overview page, you can now create and manage different issue types, including Epic, Story, Task, and Bug.

Step 3: 

To convert issue types when the scope changes, follow the guidelines below:

Issue Type has two options: Update and Conversion - allowing users to change issue classifications while maintaining consistency in the hierarchy.

Update:

You can use it to change an existing issue type into another type without losing progress or data. This feature gives teams greater flexibility when reclassifying work as project needs evolve.

For example:

• A Story can be converted into a Bug if the feature request is later identified as a defect.
• A Task can be converted into a Story if it grows in scope and needs to contain subtasks.
• A Bug can be converted into a Task if it is determined to be a general work item rather than a defect.

Note: Conversions between issue types do not affect the hierarchy. 

Conversion Flow:

The conversion process respects existing relationships and maintains data integrity:

• When a Task with Sub-tasks is converted into a Story or a Bug, the Sub-tasks remain unchanged and continue to be associated with the new parent.

• When a Task is converted to an Epic, its subtasks cannot remain linked (since Epics cannot directly hold Subtasks).
• In this case, all subtasks are automatically promoted and become standalone Tasks.

Note: You can also convert an issue type directly from the More (⋮ ) icon in the issue view.