Abstract: A method for use in an issue creation process, before an issue is submitted, in an issue tracking system (ITS), comprises receiving an unstructured user input expressing an issue description and comprising one or more query keywords; querying a database of historic issue data to determine historic issues from the historic issue data that are relevant to the one or more query keywords and, in response to the determination, extracting request types from the historic issues; generating, from the extracted request types, a list of possible request types for allocation to the unstructured user input; receiving a user input of a particular request type selected from the list of possible request types and, in response, allocating the particular request type to the issue. The issue is submitted to the ITS for routing the issue to an appropriate service desk according to the particular request type.

Abstract: A computer-implemented method is disclosed. The method comprises receiving a notification from a job scheduler that an execution time for a job registered with the job scheduler is at or before a first time being a current time. The method also comprises identifying, in response to receiving the notification, at least one task from a task data structure with a target runtime that is at or before the first time. The task data structure stores task data for one or more tasks received from one or more client computers, and the task data associates each of the one or more tasks with a target runtime. The method further comprises initiating execution for each of the at least one task and determining whether there is a specific task from the task data structure with a specific target runtime after the first time.

Abstract: A method for use in an issue creation process in an issue tracking system includes receiving an issue description comprising keywords, querying a database of historic issue data representing historic issues maintained by the issue tracking system, the historic issues defined by at least a request type and request data. Querying comprises searching the database of historic issue data using the keywords, locating one or more historic issues that include the keywords in its request data, extracting the request type of each of the located historic issues, selecting request types based on a popularity of each request type amongst the located historic issues, generating a list of possible request types for allocation to the issue description, and allocating a particular request type to an issue corresponding to the issue description in response to receiving input that selects the particular request type from among the list of possible request types.

Abstract: A method for use in an issue creation process, before an issue is submitted, in an issue tracking system (ITS), comprises receiving an unstructured user input expressing an issue description and comprising one or more query keywords; querying a database of historic issue data to determine historic issues from the historic issue data that are relevant to the one or more query keywords and, in response to the determination, extracting request types from the historic issues; generating, from the extracted request types, a list of possible request types for allocation to the unstructured user input; receiving a user input of a particular request type selected from the list of possible request types and, in response, allocating the particular request type to the issue. The issue is submitted to the ITS for routing the issue to an appropriate service desk according to the particular request type.

Abstract: A computer-implemented method is disclosed. The method comprises receiving a notification from a job scheduler that an execution time for a job registered with the job scheduler is at or before a first time being a current time. The method also comprises identifying, in response to receiving the notification, at least one task from a task data structure with a target runtime that is at or before the first time. The task data structure stores task data for one or more tasks received from one or more client computers, and the task data associates each of the one or more tasks with a target runtime. The method further comprises initiating execution for each of the at least one task and determining whether there is a specific task from the task data structure with a specific target runtime after the first time.

Abstract: Disclosed herein is a computer implemented method for scheduling a new task. The method comprises: receiving task data in respect of the new task, the task data comprising at least information enabling the new task to be uniquely identified and a target runtime for the new task; recording the received task data in a data structure and determining if a new job needs to be registered with an underlying job scheduler.

Abstract: A method for use in an issue creation process in an issue tracking system includes receiving an issue description comprising keywords, querying a database of historic issue data representing historic issues maintained by the issue tracking system, the historic issues defined by at least a request type and request data. Querying comprises searching the database of historic issue data using the keywords, locating one or more historic issues that include the keywords in its request data, extracting the request type of each of the located historic issues, selecting request types based on a popularity of each request type amongst the located historic issues, generating a list of possible request types for allocation to the issue description, and allocating a particular request type to an issue corresponding to the issue description in response to receiving input that selects the particular request type from among the list of possible request types.

Abstract: Disclosed herein is a computer implemented method for scheduling a new task. The method comprises: receiving task data in respect of the new task, the task data comprising at least information enabling the new task to be uniquely identified and a target runtime for the new task; recording the received task data in a data structure and determining if a new job needs to be registered with an underlying job scheduler.

Abstract: Disclosed herein is a computer implemented method for scheduling a new task. The method comprises: receiving task data in respect of the new task, the task data comprising at least information enabling the new task to be uniquely identified and a target runtime for the new task; recording the received task data in a data structure and determining if a new job needs to be registered with an underlying job scheduler.

Abstract: Disclosed herein is a computer implemented method for scheduling a new task. The method comprises: receiving task data in respect of the new task, the task data comprising at least information enabling the new task to be uniquely identified and a target runtime for the new task; recording the received task data in a data structure and determining if a new job needs to be registered with an underlying job scheduler.