US 11,928,630 B2
Issue tracking systems and methods
Jascha-Alexander Stephan Zittel, Sydney (AU); Amaresh Ray, Sydney (AU); Bradley Jay Schoone, Sydney (AU); and Christopher Charles Mann, Sydney (AU)
Assigned to ATLASSIAN PTY LTD., Sydney (AU); and ATLASSIAN US, INC., San Francisco, CA (US)
Filed by Atlassian Pty Ltd., Sydney (AU); and Atlassian Inc., San Francisco, CA (US)
Filed on Apr. 25, 2022, as Appl. No. 17/728,914.
Application 17/728,914 is a continuation of application No. 16/914,419, filed on Jun. 28, 2020, granted, now 11,315,058.
Prior Publication US 2022/0253762 A1, Aug. 11, 2022
Int. Cl. G06Q 10/0633 (2023.01); G06Q 10/0631 (2023.01); G06Q 10/0635 (2023.01)
CPC G06Q 10/0633 (2013.01) [G06Q 10/06316 (2013.01); G06Q 10/0635 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computer-implemented method comprising:
in response to a change requesting system receiving a user input at a user interface of the change requesting system to perform an operation and in response to the change requesting system determining that the operation is a gated operation and disabling a corresponding control of the operation, receiving, at a software instance of an issue tracking system instantiated over at least one processor, an operation notification from the change requesting system, the operation notification being in respect of the gated operation to be performed by the change requesting system;
in response to receiving the operation notification at the software instance of the issue tracking system:
determining an operation classification based on one or more parameters of the operation notification;
identifying an issue managed by the issue tracking system and corresponding to the operation of the operation notification, the issue associated with a predefined workflow of multiple workflow states defined by the issue tracking system, the multiple workflow states including at least one pending workflow state and at least one operation resolution workflow state;
computing a risk value for the identified issue based on the operation classification and one or more first attributes of the identified issue managed by the issue tracking system; and
retrieving an automation rule based on one or more second attributes of the identified issue and evaluating the automation rule with respect to one or more conditions of the issue tracking system and the computed risk value, the automation rule causing the issue tracking system to automatically transition the issue from a first workflow state to a second workflow state; and
automatically communicating a message regarding the workflow state transition from the issue tracking system to the change requesting system, thereby causing the change requesting system to reenable the corresponding control of the operation in the user interface of the change requesting system.