CAPTURING EFFORT LEVEL BY TASK UPON CHECK-IN TO SOURCE CONTROL MANAGEMENT SYSTEM
First Claim
1. A computer-implemented method comprising:
- receiving input representing a proposed change to a software source file;
in response to the input, capturing an effort level and task ID associated with the proposed change;
making said proposed change;
storing data that indicates the task ID; and
storing data, in association with the task ID, that indicates the effort level.
2 Assignments
0 Petitions
Accused Products
Abstract
Techniques are provided for capturing the ID of a work item, and the corresponding effort level information, as a part of the actual check-in process of the artifacts into the underlying change management system. This effort information can then be propagated to an external system for subsequent reporting and analysis. In one embodiment, tasks (or similar items such as issues or bugs) are entered into a common task or issue tracking system. As part of this process each task is assigned a unique identifier. A “call-out” is added to the source control management system which captures the effort level and task ID associated with the proposed change. The data entered is validated to ensure that the task ID is valid and that the effort entered is within a valid range. If the data entered is valid, the change to the underlying artifact is allowed to proceed and the effort and task information is stored for later analysis. If the data is not valid, the proposed change is rejected and an appropriate error message is returned to the user.
-
Citations
8 Claims
-
1. A computer-implemented method comprising:
-
receiving input representing a proposed change to a software source file; in response to the input, capturing an effort level and task ID associated with the proposed change; making said proposed change; storing data that indicates the task ID; and storing data, in association with the task ID, that indicates the effort level. - View Dependent Claims (2, 3, 4)
-
-
5. A computer-readable storage medium comprising instructions for:
-
receiving input representing a proposed change to a software source file; in response to the input, capturing an effort level and task ID associated with the proposed change; making said proposed change; storing data that indicates the task ID; and storing data, in association with the task ID, that indicates the effort level. - View Dependent Claims (6, 7, 8)
-
Specification