Configurable Issue Type Hierarchy Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing issue tracking systems face challenges in managing relationships between issue types and hierarchy levels, particularly when changes to issue type properties render existing relationships invalid.

Innovation Solution

A computer-implemented method and system that allow users to change the hierarchy level of an issue type by updating the associated hierarchy-issue type association data records in a data store, while also breaking invalid relationships and maintaining the integrity of the issue type hierarchy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users are allowed to create and use different issue types with customizable properties, then the system provides flexibility and adaptability, but managing issue types and their relationships becomes difficult and complex

Engineering Contradiction:
Improveflexibility in creating and using different issue typesVSAvoidcomplexity of managing issue types and relationships
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the issue type management by introducing a hierarchical structure with multiple levels (e.g., level 1, level 2, level 3). Each issue type is assigned to a specific hierarchy level, which divides the complex management into manageable segments. This segmentation allows users to organize issue types in a structured manner, reducing the complexity of managing relationships between numerous issue types while preserving flexibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces hierarchy level as a new parameter for issue types. By assigning issue types to different hierarchy levels, the system creates a structured framework that simplifies relationship management. The hierarchy level parameter acts as an organizing dimension that reduces complexity while maintaining the ability to create and customize diverse issue types.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If properties of an issue type are changed to improve adaptability, then the system becomes more flexible, but existing relationships associated with that issue type become invalid

Engineering Contradiction:
Improveability to change issue type propertiesVSAvoidvalidity of existing issue relationships
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements preliminary validation before allowing issue type property changes. The system checks whether the proposed changes would invalidate existing relationships and prompts users to resolve these conflicts before applying changes. This preliminary action prevents relationship invalidation while maintaining adaptability, as users are guided through the necessary steps to preserve relationship integrity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces feedback mechanisms that inform users about the impact of proposed issue type changes. When users attempt to modify issue type properties, the system provides feedback about affected relationships and requires user confirmation or resolution. This feedback loop ensures that changes maintain reliability by preventing invalid relationships while preserving the ability to adapt issue type properties.

Inventive Principle:
Principle #23Feedback

3Reliability

If the system enforces strict relationship rules to maintain integrity, then relationship validity is preserved, but the system becomes less flexible in allowing issue type changes

Engineering Contradiction:
Improveintegrity of issue relationshipsVSAvoidflexibility in changing issue type hierarchy levels
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic relationship validation that adapts to the hierarchical structure. Instead of static, rigid rules, the system dynamically evaluates relationship validity based on hierarchy levels. This allows issue type changes within the same hierarchy level or across appropriate levels while maintaining relationship integrity. The dynamic approach preserves reliability through structured validation while enabling flexibility in legitimate hierarchy modifications.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20250139582A1Issue tracking systems and methods for a configurable project hierarchy
Publication Date: 2025.05.01 ATLASSIAN PTY LTD
  • US20250139582A1 patent drawing
  • US20250139582A1 patent drawing
  • US20250139582A1 patent drawing

AI summary

Described herein are systems, methods and computer-readable media for maintaining a configurable project hierarchy. The method includes establishing a project hierarchy with multiple hierarchy levels including first and second hierarchy levels. The first level has an associated issue type. The method further includes receiving a request to change the hierarchy level of the first issue type to the second level. In response to receiving this request, the method includes: accessing from a data store, a hierarchy-issue type association record of the first issue type including an identifier of the first issue type and a current hierarchy level identifier; creating a new hierarchy-issue type association data record including the identifier of the first issue type and a new hierarchy level identifier corresponding to the second hierarchy level; and associating the first issue type with the second hierarchy level by storing the new hierarchy/issue type association data record in the data store.