0004746: Version freeze VS. Baseline

testlink.org

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0004746

TestLink

Requirement Version Compare

public

2011-09-13 11:00

2015-04-26 15:37

Reporter

mike_w

Assigned To

Priority

normal

Severity

feature request

Reproducibility

always

Status

new

Resolution

open

Platform

linux - gentoo

OS Version

2.6.35 Kernel

Product Version

1.9.2 (2011 Q2 - bug fixing)

Fixed in Version

Summary

0004746: Version freeze VS. Baseline

Description

Version freeze is not applicable for practical baseline management.
Example:

First Draft of specification
Req1: Version 0, Revision 1
Req2: Version 0, Revision 2
Req3: Version 0, Revision 1
-- freeze of first draft --

second draft of specification
Req1: Version 0, Revision 1 , no changes
Req2: Version 1, Revision 1 , changes
Req3: Version 0, Revision 1 , no changes
Req4: Version 0, Revision 1 , new requirement
-- freeze of second draft --

first release of specification
Req1: Version 1, Revision 2 , changes
Req2: Version 2, Revision 1 , small changes
-Req3: Version 0, Revision 1 , deleted
Req4: Version 0, Revision 1 , new requirement
-- freeze of first release --

And now we had to reproduce the version of "second draft of specification" at the moment of freeze. -> At the moment, this is NOT possible.

A index table for an release with all versions and revisions should be made at a moment of freeze. This 'baseline' should also be available as report.

Tags

No tags attached.

Database (MySQL,Postgres,etc)

mysql

Browser

PHP Version

TestCaseID

QA Team - Task Workflow Status

Attached Files

Relationships

parent of	0004766	closed	fman	Requirements Report - Display Revision and Version
parent of	0004767	closed	fman	Req Spec Export - Export Revision
child of	0004768	closed	fman	Requirements Export - Export Version and Revision
child of	0007083	new		Mantis Issues proposed to be closed

Notes
(0015876) mike_w (reporter) 2011-10-06 10:00	A quick solution for this problem could be a add of the fields version and revision in the specification export. The export is than the baseline with the reference to requirements version and revisions. At the moment the field version and revision are not displayed in the export. Could this easily changed? (by config file or little change in script?)

(0015879) fman (administrator) 2011-10-07 06:37	@mike_w Please open a new issue that is what you have explained on not 15876. This way we will leave THIS ISSUE LIVE, add a relationship bewteee both, and try to work on new issue (may be we can create a quick fix).

(0015880) mike_w (reporter) 2011-10-07 06:49	New ticket 0004766 for quick solution created.

Issue History
Date Modified	Username	Field	Change
2011-09-13 11:00	mike_w	New Issue
2011-10-06 10:00	mike_w	Note Added: 0015876
2011-10-07 06:37	fman	Note Added: 0015879
2011-10-07 06:49	mike_w	Note Added: 0015880
2011-10-07 07:02	fman	Relationship added	parent of 0004766
2011-10-07 18:58	fman	Relationship added	parent of 0004767
2011-10-07 18:59	fman	Relationship added	child of 0004768
2015-04-26 15:37	Mr.Bricodage	Relationship added	child of 0007083