IP Library › Granted Patent US 11,416,124
Granted Patent B2
US 11,416,124 · App. 16/920,139 · Granted Aug 16, 2022

Graphical computer interface for an issue tracking system

Inventor: Jacob Bass (Sydney, AU)
Assignees: ATLASSIAN PTY LTD.; ATLASSIAN INC.
G06F3/0484G06F3/0482G06Q10/06316G06Q30/016
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,416,124
App. No.
16/920,139
Granted
Aug 16, 2022
Kind
B2
Abstract

Described herein is an issue tracking system (ITS) comprising one or more processors; 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: render a user interface depicting an issues queue that includes two or more issues defined in the ITS; receive in the user interface, a selection of at least two issues; receive in the user interface a section of an action; and launch an operation to apply the selected action to each selected issue.

Claims (76)

1. An issue tracking system (ITS) comprising:

one or more processors;

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:

render a user interface depicting:

a heading region comprising a set of column headings, each respective column heading identifying a respective issue ticket attribute; and

an issue ticket region below the heading region and displaying an issue ticket queue that includes a plurality of issue tickets defined in the ITS, wherein a displayed issue ticket includes a respective value for each of at least a subset of the issue ticket attributes displayed in the column headings;

receive, in the user interface, a selection of at least two issue tickets of the plurality of issue tickets;

in response to receiving the selection of the at least two issue tickets:

cease displaying the set of column headings in the heading region of the user interface; and

display, in the heading region of the user interface, a set of actions of a plurality of candidate actions, the set of actions selected based at least in part on the at least two issue tickets;

receive, in the user interface, a selection of an action of the set of actions; and

in response to receiving the selection of the action of the set of actions:

launch an operation to apply the selected action to the at least two issue tickets;

cease displaying the set of actions in the heading region; and

display the set of column headings in the heading region.

2. The ITS according to claim 1 , wherein:

the selection of the at least two issue tickets is a first selection of at least two first issue tickets;

the set of actions is a first set of actions;

the operation is a first operation;

the selection of an action is a first selection of a first action; and

the sequences of instructions are further configured to cause the one or more processors to:

receive, in the user interface, a second selection of at least two second issue tickets of the plurality of issue tickets, the at least two second issue tickets different than the at least two first issue tickets;

in response to receiving the second selection of the at least two second issue tickets:

cease displaying the set of column headings in the heading region of the user interface; and

display, in the heading region of the user interface, a second set of actions of the plurality of candidate actions, the second set of actions selected based at least in part on the at least two second issue tickets and different from the first set of actions;

receive, in the user interface, a second selection of a second action of the second set of actions;

launch an operation to apply the selected second action to the at least two second issue tickets

cease displaying the second set of actions in the heading region; and

display the set of column headings in the heading region.

3. The ITS according to claim 2 , wherein the first set of actions and the second set of actions are selected by reference to an agent authorisation level.

4. The ITS according to claim 2 , wherein:

the first set of actions is selected by reference to transition rules defined for the at least two first issue tickets; and

the second set of actions is selected by reference to transition rules defined for the at least two second issue tickets.

5. The ITS according to claim 2 , wherein the first set of actions includes linking the at least two first issue tickets to a common incident and transitioning the at least two first issue tickets to another status.

6. The ITS according to claim 1 , wherein the instructions further cause the processor to disable mutability of the issue ticket queue upon detecting a selection of an issue ticket.

7. The ITS according to claim 1 , wherein the instructions further cause the processor to prevent selection of further issue tickets upon detecting a selection of the action.

8. The ITS according to claim 1 , wherein the instructions further cause the processor to render a user interface including a quantitative report of the issue tickets to which the selected action was successfully applied.

9. The ITS according to claim 2 , wherein the actions of the first set of actions are selected, from the plurality of candidate actions, based on a determination that each action of the first set of actions is applicable to the at least two first issue tickets.

10. The ITS according to claim 9 , wherein at least one action of the first second set of actions is not applicable to at least one of the at least two second issue tickets.

11. A computer implemented method comprising:

rendering a user interface of an issue tracking system (ITS), the user interface depicting:

a heading region comprising a set of column headings, each respective column heading identifying a respective issue ticket attribute; and

an issue ticket region below the heading region and displaying an issue ticket queue that includes a plurality of issue tickets defined in the ITS, wherein a displayed issue ticket includes a respective value for each of at least a subset of the issue ticket attributes displayed in the column headings;

receiving, in the user interface, a selection of at least two issue tickets of the plurality of issue tickets;

in response to receiving the selection of the at least two issue tickets:

cease displaying the set of column headings in the heading region of the user interface; and

displaying, in the heading region of the user interface, a set of actions of a plurality of candidate actions, the set of actions selected based at least in part on the at least two issue tickets;

receiving, in the user interface, a selection of an action of the set of actions; and

in response to receiving the selection of the action of the set of actions:

launching an operation to apply the selected action to the at least two issue tickets;

cease displaying the set of actions in the heading region; and

displaying the set of column headings in the heading region.

12. The method according to claim 11 , wherein:

the selection of the at least two issue tickets is a first selection of at least two first issue tickets;

the set of actions is a first set of actions;

the operation is a first operation;

the selection of an action is a first selection of a first action; and

the method further includes:

receiving, in the user interface, a second selection of at least two second issue tickets of the plurality of issue tickets, the at least two second issue tickets different than the at least two first issue tickets;

in response to receiving the second selection of the at least two second issue tickets:

cease displaying the set of column headings in the heading region of the user interface; and

displaying, in the heading region of the user interface, a second set of actions of the plurality of candidate actions, the second set of actions selected based at least in part on the at least two second issue tickets and different from the first set of actions;

receiving, in the user interface, a second selection of a second action of the second set of actions;

launching an operation to apply the selected second action to the at least two second issue tickets

cease displaying the second set of actions in the heading region; and

displaying the set of column headings in the heading region.

13. The method according to claim 12 , wherein the first set of actions and the second set of actions are selected by reference to an agent authorisation level.

14. The method according to claim 13 , wherein:

the first set of actions is selected by reference to transition rules defined for the at least two first issue tickets; and

the second set of actions is selected by reference to transition rules defined for the at least two second issue tickets.

15. The method according to claim 12 , wherein the first set of actions includes linking the at least two first issue tickets to a common incident and transitioning the at least two first issue tickets to another status.

16. The method according to claim 11 , further including disabling mutability of the issue ticket queue upon detecting a selection of an issue ticket.

17. The method according to claim 11 , further including preventing selection of further issue tickets upon detecting a selection of the action.

18. The method according to claim 11 , further including rendering a user interface including a quantitative report of the issue tickets to which the selected action was successfully applied.

19. The method according to claim 12 , wherein the actions of the first set of actions are selected, from the plurality of candidate actions, based on a determination that each action of the first set of actions is applicable to the at least two first issue tickets.

20. The method according to claim 19 , wherein at least one action of the first set of actions is not applicable to at least one of the at least two second issue tickets.

Assignments (2)
CHANGE OF NAME Recorded Aug 5, 2022
From: ATLASSIAN, INC.
To: ATLASSIAN US, INC.
Reel/Frame 061085/0690 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 11, 2020
From: BASS, JACOB
To: ATLASSIAN PTY LTD.; ATLASSIAN INC.
Reel/Frame 053460/0878 →
Continuity (1)
Related Publication 20220004296A1 · Jan 6, 2022
Cited By (1)
US 12,307,071