Abstract: A method including operations of displaying a scheduling interface including a first work item user interface element corresponding to a first work item, the first work item user interface element displayed to visually indicate a scheduled start date of the first work item and a scheduled end date for the first work item; receiving forecast data generated in respect of the first work item; determining, based on the forecast data, a first forecast range in respect of the first work item; and displaying a first forecast user interface element on the scheduling interface, the first forecast user interface element corresponding to the first work item and having an appearance based on the first forecast range.

Abstract: A method including operations of displaying a scheduling interface including a first work item user interface element corresponding to a first work item, the first work item user interface element displayed to visually indicate a scheduled start date of the first work item and a scheduled end date for the first work item; receiving forecast data generated in respect of the first work item; determining, based on the forecast data, a first forecast range in respect of the first work item; and displaying a first forecast user interface element on the scheduling interface, the first forecast user interface element corresponding to the first work item and having an appearance based on the first forecast range.

Abstract: Systems and methods for exporting data from a cloud server and/or importing data to a cloud server are disclosed. The method for exporting data includes receiving a plurality of event records. Each event record includes information about an update to application data of an application. The computer-implemented method further including storing the plurality of event records in near real-time in a predefined storage location and in response to a client export request, creating one or more backup files based on the stored event records in the predefined storage location, and allowing export of the one or more backup files to a local client storage location.

Abstract: Described herein is a computer implemented method. The method comprises generating a subscription identifier based on an original SQL query and determining if a set of first stage query results is associated with the subscription identifier in a cache. If so, the method further comprises generating a second stage SQL query based on a second subset of the plurality of clauses and the set of first stage query results, causing execution of the second stage SQL query to obtain a set of second stage query results from a database, and returning the set of second stage query results.

Abstract: Described herein is a computer implemented method. The method comprises generating a subscription identifier based on an original SQL query and determining if a set of first stage query results is associated with the subscription identifier in a cache. If so, the method further comprises generating a second stage SQL query based on a second subset of the plurality of clauses and the set of first stage query results, causing execution of the second stage SQL query to obtain a set of second stage query results from a database, and returning the set of second stage query results.

Abstract: An issue tracking system (ITS) is disclosed. The ITS comprises a user interface configured to receive user input defining one or more issues and an interface module configured to interface with a source code management system (SCM) and receive from the SCM, data pertaining to linked SCM-repository events. The received data is processed to generate an order for the SCM-repository events to which the issue is linked. A display module is configured to concurrently display a plurality of issues, each issue being displayed with issue information and issues having linked SCM-repository events being displayed with linked SCM-repository event information, said linked SCM-repository event information being displayed according to the generated order.

Abstract: An issue tracking system (ITS) is disclosed. The ITS comprises a user interface configured to receive user input defining one or more issues and an interface module configured to interface with a source code management system (SCM) and receive from the SCM, data pertaining to linked SCM-repository events. The received data is processed to generate an order for the SCM-repository events to which the issue is linked. A display module is configured to concurrently display a plurality of issues, each issue being displayed with issue information and issues having linked SCM-repository events being displayed with linked SCM-repository event information, said linked SCM-repository event information being displayed according to the generated order.

Abstract: Described herein is a computer implemented method. The method comprises processing clauses included in an original SQL query to add each clause to either a set of caching clauses or a set of non-caching clauses and determining whether a subscription should be created. In response to determining the subscription should be created, the method comprises creating the subscription by generating a first stage SQL query based on the set of caching clauses, causing execution of the first stage SQL query to obtain a set of first stage query results from a database; and storing the set of first stage query results in a cache.

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.

Abstract: Described herein is a computer implemented method. The method comprises processing clauses included in an original SQL query to add each clause to either a set of caching clauses or a set of non-caching clauses and determining whether a subscription should be created. In response to determining the subscription should be created, the method comprises creating the subscription by generating a first stage SQL query based on the set of caching clauses, causing execution of the first stage SQL query to obtain a set of first stage query results from a database; and storing the set of first stage query results in a cache.

Abstract: Described herein is a computer implemented method. The method comprises generating a subscription identifier based on an original SQL query and determining if a set of first stage query results is associated with the subscription identifier in a cache. If so, the method further comprises generating a second stage SQL query based on a second subset of the plurality of clauses and the set of first stage query results, causing execution of the second stage SQL query to obtain a set of second stage query results from a database, and returning the set of second stage query results.

Abstract: A method including operations of displaying a scheduling interface including a first work item user interface element corresponding to a first work item, the first work item user interface element displayed to visually indicate a scheduled start date of the first work item and a scheduled end date for the first work item; receiving forecast data generated in respect of the first work item; determining, based on the forecast data, a first forecast range in respect of the first work item; and displaying a first forecast user interface element on the scheduling interface, the first forecast user interface element corresponding to the first work item and having an appearance based on the first forecast range.

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.

Abstract: A method including operations of displaying a scheduling interface including a first work item user interface element corresponding to a first work item, the first work item user interface element displayed to visually indicate a scheduled start date of the first work item and a scheduled end date for the first work item; receiving forecast data generated in respect of the first work item; determining, based on the forecast data, a first forecast range in respect of the first work item; and displaying a first forecast user interface element on the scheduling interface, the first forecast user interface element corresponding to the first work item and having an appearance based on the first forecast range.

Abstract: A method including operations of displaying a scheduling interface including a first work item user interface element corresponding to a first work item, the first work item user interface element displayed to visually indicate a scheduled start date of the first work item and a scheduled end date for the first work item; receiving forecast data generated in respect of the first work item; determining, based on the forecast data, a first forecast range in respect of the first work item; and displaying a first forecast user interface element on the scheduling interface, the first forecast user interface element corresponding to the first work item and having an appearance based on the first forecast range.

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.

Abstract: An issue tracking system (ITS) is disclosed. The ITS comprises a user interface configured to receive user input defining one or more issues and an interface module configured to interface with a source code management system (SCM) and receive from the SCM, data pertaining to linked SCM-repository events. The received data is processed to generate an order for the SCM-repository events to which the issue is linked. A display module is configured to concurrently display a plurality of issues, each issue being displayed with issue information and issues having linked SCM-repository events being displayed with linked SCM-repository event information, said linked SCM-repository event information being displayed according to the generated order.

Abstract: An issue tracking system (ITS) is disclosed. The ITS comprises a user interface configured to receive user input defining one or more issues and an interface module configured to interface with a source code management system (SCM) and receive from the SCM, data pertaining to linked SCM-repository events. The received data is processed to generate an order for the SCM-repository events to which the issue is linked. A display module is configured to concurrently display a plurality of issues, each issue being displayed with issue information and issues having linked SCM-repository events being displayed with linked SCM-repository event information, said linked SCM-repository event information being displayed according to the generated order.

Abstract: An issue tracking system (ITS) is disclosed. The ITS comprises a user interface configured to receive user input defining one or more issues and an interface module configured to interface with a source code management system (SCM) and receive from the SCM, data pertaining to linked SCM-repository events. The received data is processed to generate an order for the SCM-repository events to which the issue is linked. A display module is configured to concurrently display a plurality of issues, each issue being displayed with issue information and issues having linked SCM-repository events being displayed with linked SCM-repository event information, said linked SCM-repository event information being displayed according to the generated order.