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.

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: Techniques are provided for manifesting a multiple repository system as a single repository to an application that is designed to use a single repository. According to one aspect, a particular container, which is used by the application to store data, is identified. One or more additional containers are created in one or more different repositories. Each of the additional containers is formatted to store the data that the application stores in the particular container. A construct is created. The construct is associated with the particular container's identifier. The construct causes information from the particular container and each of the additional containers to be combined to answer database commands that reference the particular container's identifier. As a result, data stored in a single repository can be distributed among multiple repositories, and the unmodified application can continue to access that data as though the data was stored in the single repository.

Abstract: Techniques are provided for manifesting a multiple repository system as a single repository to an application that is designed to use a single repository. According to one aspect, a particular container, which is used by the application to store data, is identified. One or more additional containers are created in one or more different repositories. Each of the additional containers is formatted to store the data that the application stores in the particular container. A construct is created. The construct is associated with the particular container's identifier. The construct causes information from the particular container and each of the additional containers to be combined to answer database commands that reference the particular container's identifier. As a result, data stored in a single repository can be distributed among multiple repositories, and the unmodified application can continue to access that data as though the data was stored in the single repository.

Abstract: Techniques are provided for manifesting a multiple repository system as a single repository to an application that is designed to use a single repository. According to one aspect, a particular container, which is used by the application to store data, is identified. One or more additional containers are created in one or more different repositories. Each of the additional containers is formatted to store the data that the application stores in the particular container. A construct is created. The construct is associated with the particular container's identifier. The construct causes information from the particular container and each of the additional containers to be combined to answer database commands that reference the particular container's identifier. As a result, data stored in a single repository can be distributed among multiple repositories, and the unmodified application can continue to access that data as though the data was stored in the single repository.