Support for "Change" object

[twelveeighty]

We're still new to using Testlink and we like what we see so far. However, in addition to the "Requirements" and "Test" objects, I'd like to know if anyone else has any need for a "Change" object? I mean "Change" in the ITIL sense (incident, problem, Change, ...).

A "Change" would be "how" a Requirement gets implemented before it can be Tested in a Test Plan. There is a many-to-many relationship between Requirements, Changes and Test Cases: a single Requirement may require multiple Changes, and a single Change may implement many Requirements.

Attributes of a "Change" would be a description of the "how" i.e. its design, design approval, estimated and actual implementation effort, etc.

I would most likely either try to implement this in Testlink ourselves, or try to integrate with a 3rd party tool. If there is a lot of interest, we may want to make the investment of changing Testlink and submitting our code.

Any thoughts?

[fman]

if you consider this a feature request, please open an issue on mantis and attach a word or open office document with as much as possible details, considering also if possible interaction with current TL implementation and side effects.
As far as I have understood from your lines, I do not think is TL has to be the place to manage this kind of object.
We are already managing requirements when our initial focus was only test cases, then if a change can be an issue, the right place for it is IMHO a Issue tracking system.

Anyway open the issue, and we will can discuss in future (after release of 1.9 General Availability) about this

regards

Francisco