Abstract: Systems and processes for migration of data stored in a label-based software configuration management (CM) system to records of a time-based CM system in a manner that permits for identification, in the time-based system, of contents of releases. In some exemplary implementations, techniques operating according to some of the principles described herein will accept as input information relating to a listing of a label-based system and estimate, based on the software component versions in the listing and their corresponding creation times, a release time indicating a time a release was created. The release time may then be used, in some, but not necessarily all, implementations to create a data structure in the time-based system indicating contents of the version at the particular time. Some exemplary implementations may additionally determine, from the estimated release time, whether any software component versions should be explicitly included or excluded from the data structure.

Abstract: Embodiments of the invention are directed to systems and processes for enabling querying of one or more data stores of CM applications using a graphical user interface (GUI) by which a user (e.g., a developer, supervisor, or project team leader) may select search terms. The GUI may offer one or more types of categories of search terms illustrated at a high level, such that a user may select search terms without knowledge of the underlying data structure of the data store(s). In some embodiments of the invention, when search results are presented to the user issuing a query, the search results are presented in a GUI that permits the users to make edits to the data without opening other windows to make the changes. For example, in some embodiments of the invention, the user may be permitted to select one or more results and “drag” the results, using the GUI, to another element of the GUI to make a change to the data, or may perform any other graphical operation with the results.

Abstract: A platform is provided for enabling developers to customize easily and efficiently the performance of tasks on versions of a software project. An interface may be established in a software configuration management (SCM) application for communicating with software analysis processes, and information about a manner in which the software analysis process is triggered or stores data may be input as parameters to the interface. Additionally, generic parameters for a task to be performed by the software analysis process may be provided in a template. The template may then be provided to developers to populate with specific parameters regarding the particular task that developer would like performed, such as to identifying information for a version and a condition upon which the task is to be performed. Each developer of a team may make use of the template and the interface to customize the automation of tasks that he/she would like performed.

Abstract: Embodiments of the invention are directed to a configuration management (CM) system, method, and product adapted to carry out workflow management tasks, which integrates status of software projects and issues, such that software projects may be more easily and reliably tracked and management of software projects may be streamlined. In some embodiments of the invention, a CM system is adapted to maintain records of software projects and/or issues managed by the CM system, the records comprising an indicator of a workflow progress stage for the project/issue. The CM system may be further adapted to update concurrently and automatically, according to an input from a user, both (1) a workflow progress stage value for the project/issue and (2) a record for software code associated with a project/issue, the record for the software code indicating a version and the project/issue in which the version is included.

Abstract: Embodiments of the invention are directed to a configuration management (CM) system, method, and product adapted to carry out workflow management tasks, which integrates status of software projects and issues, such that software projects may be more easily and reliably tracked and management of software projects may be streamlined. In some embodiments of the invention, a CM system is adapted to maintain records of software projects and/or issues managed by the CM system, the records comprising an indicator of a workflow progress stage for the project/issue. The CM system may be further adapted to update concurrently and automatically, according to an input from a user, both (1) a workflow progress stage value for the project/issue and (2) a record for software code associated with a project/issue, the record for the software code indicating a version and the project/issue in which the version is included.

Abstract: A platform is provided for enabling developers to customize easily and efficiently the performance of tasks on versions of a software project. An interface may be established in a software configuration management (SCM) application for communicating with software analysis processes, and information about a manner in which the software analysis process is triggered or stores data may be input as parameters to the interface. Additionally, generic parameters for a task to be performed by the software analysis process may be provided in a template. The template may then be provided to developers to populate with specific parameters regarding the particular task that developer would like performed, such as to identifying information for a version and a condition upon which the task is to be performed. Each developer of a team may make use of the template and the interface to customize the automation of tasks that he/she would like performed.

Abstract: Systems and methods for providing a user interface that enables a user, for example, a developer, to indicate whether to include a software component, for example, a file or directory, in a view of a version of a software development project. The user's indication may be recorded along with a time at which the indication was recorded or a transaction number representative of the time in which the indication was recorded. Systems and methods are provided for determining one or more software components of a software development project included within a view of a version of the software development project at a particular time, for example, some time in the past.

Abstract: Systems and methods for automatically determining, for a version of a software developing project, which software component versions defined for an issue resolution at a particular time, for example, a time in the past, are included in the project version at the particular time. Such determination may include determining the software component versions included in an issue resolution at a particular time, and, for each determined version, determining whether the version is included in the project version. The software components that should be propagated to other versions of a software development project so that these versions have a complete issue resolution may be determined. Further, differences between software project versions, from an issue resolution prospective, may be determined.

Abstract: Systems and methods for providing a user interface that enables a user, for example, a developer, to indicate whether to include a software component, for example, a file or directory, in a view of a version of a software development project. The user's indication may be recorded along with a time at which the indication was recorded or a transaction number representative of the time in which the indication was recorded. Systems and methods are provided for determining one or more software components of a software development project included within a view of a version of the software development project at a particular time, for example, some time in the past.

Abstract: Systems and methods for automatically determining, for a version of a software developing project, which software component versions defined for an issue resolution at a particular time, for example, a time in the past, are included in the project version at the particular time. Such determination may include determining the software component versions included in an issue resolution at a particular time, and, for each determined version, determining whether the version is included in the project version. The software components that should be propagated to other versions of a software development project so that these versions have a complete issue resolution may be determined. Further, differences between software project versions, from an issue resolution prospective, may be determined.