IP Library › Granted Patent US 11,238,030

Granted Patent B2

US 11,238,030 · App. 16/833,299 · Granted Feb 1, 2022

Issue tracking systems and methods for a configurable project hierarchy

Inventors: Ed Zhang (Sydney, AU); Nhat Tran (Sydney, AU); Albert Kavelar (Sydney, AU); Bree Davies (Sydney, AU); Andre Van Der Schyff (Sydney, AU)

Assignees: ATLASSIAN PTY LTD.; ATLASSIAN INC.

G06F16/2379 G06F16/2291

View Patent ↗

Loading inventors, assignments & file history…

Monitor This Case

Get email alerts when status or documents change.

Order Certified Copies

Most orders are placed with the USPTO same day — all within 24 business hours.

Order via The Patent Place →

Pre-filled with this patent's details

Quick Facts

Patent No.: US 11,238,030
App. No.: 16/833,299
Granted: Feb 1, 2022
Kind: B2

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

Described herein is 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.

Claims (127)

1. A computer implemented method for maintaining a configurable project hierarchy, the computer implemented method comprising:

receiving, from a user device, a first request to add a new hierarchy level to the configurable project hierarchy;

in response to receiving the first request to add the new hierarchy level to the configurable project hierarchy:

creating a new hierarchy level data record corresponding to the new hierarchy level, the new hierarchy level data record including a new hierarchy level identifier; and

adding the new hierarchy level to the configurable project hierarchy by:

storing the new hierarchy level data record in a data store;

determining that the new hierarchy level is to be added above a below hierarchy level;

accessing a below hierarchy level data record from the data store, the below hierarchy level data record comprising below hierarchy data corresponding to the below hierarchy level;

determining, from the below hierarchy level data record, whether the below hierarchy level has an existing parent hierarchy level; and

in response to determining that the below hierarchy level does not have the existing parent hierarchy level, editing the below hierarchy level data record to record the new hierarchy level as a parent hierarchy level of the below hierarchy level;

receiving, from the user device, a second request to associate a particular issue type with the new hierarchy level; and

in response to receiving the second request to associate the particular issue type with the new hierarchy level:

creating a new hierarchy and issue type association data record including a particular issue type identifier and the new hierarchy level identifier; and

associating the particular issue type with the new hierarchy level by storing the new hierarchy and issue type association data record in the data store.

2. The computer implemented method of claim 1 , wherein adding the new hierarchy level to the configurable project hierarchy further comprises:

determining that the new hierarchy level is to be added below an above hierarchy level; and

creating the new hierarchy level data record to include an above hierarchy level identifier as a parent hierarchy level of the new hierarchy level.

3. The computer implemented method of claim 2 , wherein adding the new hierarchy level to the configurable project hierarchy further comprises:

accessing an above hierarchy level data record from the data store, the above hierarchy level data record having above hierarchy data corresponding to the above hierarchy level;

determining, from the above hierarchy level data record, whether the above hierarchy level has an existing child hierarchy level; and

in response to determining that the above hierarchy level does not have the existing child hierarchy level, editing the above hierarchy level data record to record the new hierarchy level as a child hierarchy level of the above hierarchy level.

4. The computer implemented method of claim 3 , wherein, in response to determining that the above hierarchy level record does have the existing child hierarchy level, the computer implemented method further comprises:

determining, from the above hierarchy level data record, an existing child hierarchy level identifier;

creating the new hierarchy level data record to include the existing child hierarchy level identifier as the child hierarchy level of the new hierarchy level;

editing the above hierarchy level data record to record the new hierarchy level as the child hierarchy level of the above hierarchy level;

accessing an existing child hierarchy level data record from the data store, the existing child hierarchy level data record having child hierarchy data corresponding to the existing child hierarchy level; and

editing the existing child hierarchy level data record to record the new hierarchy level as the parent hierarchy level of the existing child hierarchy level.

5. The computer implemented method of claim 1 , wherein adding the new hierarchy level to the configurable project hierarchy further comprises

creating the new hierarchy level data record to include a below hierarchy level identifier as a child hierarchy level of the new hierarchy level.

6. The computer implemented method of claim 5 , wherein, in response to determining that the below hierarchy level record does have the existing parent hierarchy level, the computer implemented method further comprises:

determining, from the below hierarchy level data record, an existing parent hierarchy level identifier;

creating the new hierarchy level data record to include the existing parent hierarchy level identifier as the parent hierarchy level of the new hierarchy level;

editing the below hierarchy level data record to record the new hierarchy level as the parent hierarchy level of the below hierarchy level;

accessing an existing parent hierarchy level data record from the data store, the existing parent hierarchy level data record having parent hierarchy data corresponding to the existing parent hierarchy level; and

editing the existing parent hierarchy level data record to record the new hierarchy level as the child hierarchy level of the existing parent hierarchy level.

7. The computer implemented method of claim 1 , further comprising:

receiving, from the user device, a third request to delete an existing hierarchy level from the configurable project hierarchy; and

in response to receiving the third request to delete the existing hierarchy level from the configurable project hierarchy, deleting the existing hierarchy level by:

accessing an existing hierarchy level data record from the data store, the existing hierarchy level data record having existing hierarchy data corresponding to the existing hierarchy level;

determining, from the existing hierarchy level data record, whether the existing hierarchy level has the parent hierarchy level and not a child hierarchy level; and

in response to determining that the existing hierarchy level has the parent hierarchy level and not the child hierarchy level:

accessing a parent hierarchy level data record from the data store, the parent hierarchy level data record having parent hierarchy data corresponding to the parent hierarchy level;

editing the parent hierarchy level data record to remove a reference to the existing hierarchy level as a child of the parent hierarchy level; and

deleting the existing hierarchy level data record from the data store.

8. The computer implemented method of claim 7 , wherein, in response to receiving the third request to delete the existing hierarchy level from the configurable project hierarchy, the method further comprises:

determining whether any issue types are associated with the existing hierarchy level; and

in response to determining that one or more issue types are associated with the existing hierarchy level, associating the one or more issue types associated with the existing hierarchy level with another hierarchy level in the configurable project hierarchy.

9. The computer implemented method of claim 1 , further comprising:

receiving, from the user device, a third request to delete an existing hierarchy level from the configurable project hierarchy; and

in response to receiving the third request to delete the existing hierarchy level from the configurable project hierarchy, deleting the existing hierarchy level by:

accessing an existing hierarchy level data record from the data store, the existing hierarchy level data record having existing hierarchy level data corresponding to the existing hierarchy level;

determining, from the existing hierarchy level data record, whether the existing hierarchy level has the parent hierarchy level and a child hierarchy level; and

in response to determining that the existing hierarchy level has the parent hierarchy level and the child hierarchy level:

accessing a parent hierarchy level data record from the data store, the parent hierarchy level data record having parent hierarchy level data corresponding to the parent hierarchy level;

editing the parent hierarchy level data record to record the child hierarchy level as a child of the parent hierarchy level;

accessing a child hierarchy level data record from the data store, the child hierarchy level data record having child hierarchy level data corresponding to the child hierarchy level;

editing the child hierarchy level data record to record the parent hierarchy level as a parent of the child hierarchy level; and

deleting the existing hierarchy level data record from the data store.

10. The computer implemented method of claim 1 , further comprising:

receiving, from the user device, a third request to delete an existing hierarchy level from the configurable project hierarchy;

determining whether any issue types are associated with the existing hierarchy level; and

in response to determining one or more issue types are associated with the existing hierarchy level, foregoing deletion of the existing hierarchy level.

11. A system comprising:

one or more processors;

a communication interface;

one or more non-transitory computer-readable storage media storing sequences of instructions which, when executed by the one or more processors, cause the one or more processors to:

receive, via the communication interface from a user device, a first request to add a new hierarchy level to a configurable project hierarchy;

in response to receiving the first request to add the new hierarchy level to the configurable project hierarchy:

create a new hierarchy level data record corresponding to the new hierarchy level, the new hierarchy level data record including a new hierarchy level identifier; and

add the new hierarchy level to the configurable project hierarchy by:

storing the new hierarchy level data record in a data store;

determining that the new hierarchy level is to be added above a below hierarchy level;

accessing a below hierarchy level data record from the data store, the below hierarchy level data record comprising below hierarchy data corresponding to the below hierarchy level;

determining, from the below hierarchy level data record, whether the below hierarchy level has an existing parent hierarchy level; and

receive, from the user device, a second request to associate a particular issue type with the new hierarchy level; and

in response to receiving the second request to associate the particular issue type with the new hierarchy level:

create a new hierarchy and issue type association data record including a particular issue type identifier and the new hierarchy level identifier; and

associate the particular issue type with the new hierarchy level by storing the new hierarchy and issue type association data record in the data store.

12. The system of claim 11 , wherein adding the new hierarchy level to the configurable project hierarchy further comprises:

determining that the new hierarchy level is to be added below an above hierarchy level; and

creating the new hierarchy level data record to include an above hierarchy level identifier as a parent hierarchy level of the new hierarchy level.

13. The system of claim 12 , wherein adding the new hierarchy level to the configurable project hierarchy further comprises:

accessing an above hierarchy level data record from the data store, the above hierarchy level data record having above hierarchy data corresponding to the above hierarchy level;

determining, from the above hierarchy level data record, whether the above hierarchy level has an existing child hierarchy level; and

in response to determining that the above hierarchy level does have the existing child hierarchy level:

determining, from the above hierarchy level data record, an existing child hierarchy level identifier;

creating the new hierarchy level data record to include the existing child hierarchy level identifier as a child hierarchy level of the new hierarchy level;

editing the above hierarchy level data record to record the new hierarchy level as the child hierarchy level of the above hierarchy level;

editing the existing child hierarchy level data record to record the new hierarchy level as the parent hierarchy level of the existing child hierarchy level.

14. The system of claim 11 , wherein adding the new hierarchy level to the configurable project hierarchy further comprises

creating the new hierarchy level data record to include a below hierarchy level identifier as a child hierarchy level of the new hierarchy level.

15. The system of claim 14 , wherein adding the new hierarchy level to the configurable project hierarchy further comprises,

in response to determining that the below hierarchy level record does have the existing parent hierarchy level:

determining, from the below hierarchy level data record, an existing parent hierarchy level identifier;

creating the new hierarchy level data record to include the existing parent hierarchy level identifier as the parent hierarchy level of the new hierarchy level;

editing the below hierarchy level data record to record the new hierarchy level as the parent hierarchy level of the below hierarchy level;

editing the existing parent hierarchy level data record to record the new hierarchy level as the child hierarchy level of the existing parent hierarchy level.

16. The system of claim 11 , wherein the sequences of instructions, when executed by the one or more processors, further cause the one or more processors to:

receive, from the user device, a third request to delete an existing hierarchy level from the configurable project hierarchy; and

in response to receiving the third request to delete the existing hierarchy level from the configurable project hierarchy, deleting the existing hierarchy level by:

accessing an existing hierarchy level data record from the data store, the existing hierarchy level data record having existing hierarchy data corresponding to the existing hierarchy level;

determining, from the existing hierarchy level data record, whether the existing hierarchy level has the parent hierarchy level and not a child hierarchy level; and

in response to determining that the existing hierarchy level has the parent hierarchy level and not the child hierarchy level:

accessing a parent hierarchy level data record from the data store, the parent hierarchy level data record having parent hierarchy data corresponding to the parent hierarchy level;

editing the parent hierarchy level data record to remove a reference to the existing hierarchy level as a child of the parent hierarchy level; and

deleting the existing hierarchy level data record from the data store.

17. The system of claim 16 , wherein, in response to receiving the third request to delete the existing hierarchy level from the configurable project hierarchy, the sequences of instructions, when executed by the one or more processors, further cause the one or more processors to:

determine whether any issue types are associated with the existing hierarchy level; and

in response to determining that one or more issue types are associated with the existing hierarchy level, associate the one or more issue types associated with the existing hierarchy level with another hierarchy level in the configurable project hierarchy.

18. The system of claim 11 , wherein the sequences of instructions, when executed by the one or more processors, further cause the one or more processors to: