Configurable Issue Tracking Hierarchies for Multi-Level Issue Types

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing issue tracking systems struggle with managing and tracking different types of issues due to the lack of flexibility in defining project-specific hierarchies, leading to difficulties in managing relationships between issue types.

Innovation Solution

The system allows users to define a configurable project hierarchy with multiple levels, associating issue types with specific hierarchy levels, enabling flexible structuring of work by allowing arbitrary numbers of hierarchy levels and user-defined associations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users are allowed to create and use different issue types with associated data and workflows, then flexibility in managing projects is improved, but difficulty in managing issues and relationships between them increases

Engineering Contradiction:
ImproveflexibilityVSAvoiddifficulty in managing issues
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments issue types into a hierarchical structure with parent and child levels. Users can create multiple levels of issue types (e.g., Epic, Story, Task, Bug) where each level serves a specific purpose. This segmentation allows complex project structures to be broken down into manageable hierarchical components, reducing the difficulty of managing diverse issue types while maintaining flexibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to issue type management by adding parent-child relationships between issue types. Instead of managing issue types as flat, independent entities, the system adds a vertical hierarchy layer that organizes issue types into structured levels. This dimensional change provides a new perspective for managing complexity, allowing users to navigate and control issue relationships through hierarchical navigation rather than managing all issue types at a single level.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If a configurable project hierarchy with multiple levels is implemented, then adaptability to project-specific needs is improved, but device complexity increases

Engineering Contradiction:
Improvecustomizable hierarchyVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements a dynamic hierarchy configuration where users can add, remove, rename, and reorganize hierarchy levels based on their specific project needs. The hierarchy structure is not fixed but can be dynamically adjusted by users through configuration interfaces. This dynamic nature allows the system to adapt to different project requirements while the underlying system manages the complexity of these changes automatically.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The hierarchy configuration system serves multiple functions: it organizes issue types, defines reporting structures, establishes workflow hierarchies, and enables flexible project structuring. A single hierarchical framework provides universal support for various project management needs, reducing the need for separate systems or complex workarounds. The multi-functional nature of the hierarchy configuration simplifies the overall system architecture while providing extensive adaptability.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250307235A1Issue tracking systems and methods for a configurable project hierarchy
Publication Date: 2025.10.02 ATLASSIAN PTY LTD
  • US20250307235A1 patent drawing
  • US20250307235A1 patent drawing
  • US20250307235A1 patent drawing

AI summary

A computer implemented method for maintaining a configurable project hierarchy. The method comprises creating a new hierarchy level data record and storing the new hierarchy level data record in a data store. The method further comprises receiving a request to associate a particular issue type with the new hierarchy level and, in response, creating a new hierarchy/issue type association data record including an identifier of the particular issue type and an identifier of the new hierarchy level identifier.