How do I use Agile Epics and User Stories in Profit.co?

In Profit.co, you can use Agile Epics and User Stories to structure work effectively, ensuring clear alignment and progress tracking.

What are Agile Epics and User Stories in Profit.co?

In Profit.co, Issue Types are structured around agile best practices. Each type plays a unique role in planning and execution:

• Epic: Represents a large body of work or strategic initiative that spans multiple sprints or projects. Epics help teams organize and monitor progress toward major business goals.
  Example: Launching a new customer mobile app.
• Story: Breaks down an Epic into smaller, user-focused requirements. Stories capture functionality from the perspective of the end user.
  Example: As a user, I want to sign up with Google so I can create an account quickly.
• Task: Represents a specific unit of work required to complete a Story. Tasks are often technical or operational in nature.
  Example: Design the Google sign-up screen.
• Sub-task: A smaller piece of work within a Task, used to split responsibilities or track granular actions.
  Example: Create UI components for the sign-up form.
• Bug: Tracks defects that need resolution to maintain quality and progress. Example: Fix the error where Google sign-up fails when an email contains special characters.

This hierarchy ensures that every piece of work is connected back to business value, while giving teams flexibility to adapt as project needs evolve.

Why use Agile Epics, Stories, and Issue Types in Profit.co?

In Profit.co, you can use Agile Epics and User Stories to structure your work effectively. Epics represent big-picture goals, while Stories capture user needs. Tasks and Sub-tasks break those needs into actionable work, and Bugs highlight defects to be fixed. This layered structure ensures that every piece of work is connected back to business value.

Key benefits:

• Plan large initiatives with Epics: Break down strategic goals (e.g., launching a new app) into manageable Stories.
• Capture user needs with Stories: Define functionality from a user’s perspective to ensure value-driven delivery.
• Organize execution with Tasks and Sub-tasks: Translate Stories into concrete work items and split them further if needed.
• Respond quickly with Bugs: Highlight issues or defects that require immediate attention without losing visibility in the overall plan.
• Stay flexible as work evolves: Convert between types as scope changes, for example, a Task becoming a Story if it needs subtasks.
• Maintain transparency & accountability: Teams can see dependencies, ownership, and progress across all levels.

Profit.co Issue Type Hierarchy at a Glance

Parent and Child Issues in Profit.co

In Profit.co, issue types follow a clear parent - child relationship that helps teams organize work at different levels:

• Epic → Parent to Stories, grouping multiple user requirements under one strategic initiative.
• Story → Parent to Tasks and Sub-tasks, breaking work into deliverable features.
• Task → Parent to Sub-tasks, dividing technical or detailed work into smaller actions.
• Sub-task → Always a child item, linked to a Task or Story, and cannot exist on its own.
• Bug → Can be linked at any level, depending on where the defect impacts the work.

This hierarchy ensures that large initiatives are broken down into smaller, actionable items while maintaining visibility of how each piece contributes to the overall goal.

How to enable Issue Types in Profit.co?

Step 1: Enable Issue Types

• 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.

Note: At the Workspace level, enable the Issue Type toggle to ensure all Boards created under it support Issue Types.

Step 2: Use Issue Types in Workspaces and Boards

Once enabled, Issue Types can be applied inside Workspaces and Boards. When creating or managing tasks, you can classify them as Epics, Stories, Tasks, Sub-tasks, or Bugs based on the work requirement.

Best Practices for Using Agile Epics and User Stories in Profit.co

• Use a clear hierarchy: Keep Epics at the strategy level, Stories at the user level, and Tasks/Sub-tasks for execution. This ensures alignment from vision to delivery.
• Prioritize by value: Always define Stories from a user’s perspective. Focus on features that provide the greatest impact before moving to technical or support tasks.
• Limit issue types: Don’t overload teams with too many classifications. Stick to Epics, Stories, Tasks, Sub-tasks, and Bugs unless you have a clear need for customization.
• Maintain consistency across teams: Standardize how issue types are used in Profit.co so reporting and progress tracking remain accurate.
• Convert when scope changes: If a Task grows into a larger feature, convert it to a Story. If a Story turns into a defect, reclassify it as a Bug. Use conversion flexibly to keep work aligned.
• Review regularly: Periodically audit your Workspaces and Boards to ensure issue types are being applied correctly and reflect your team’s current workflow.

Related Questions

Learn how to reclassify work items with Converting Agile Epics and User Stories in Profit.co, Click here.

Click here to learn more about how to create Workspaces and Boards in Profit.co.

Frequently Asked Questions