0008472: Configuration Option - Allow Add Test Case Version Relation ONLY on latest Test Case Version

testlink.org

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0008472

TestLink

Test Spec. - Test Case relations

public

2018-11-13 18:35

2018-12-16 15:34

Reporter

fman

Assigned To

fman

Priority

normal

Severity

feature request

Reproducibility

N/A

Status

resolved

Resolution

fixed

Platform

OS Version

Product Version

1.9.18 (2018 Q3)

Fixed in Version

1.9.19 (2019 Q1)

Summary

0008472: Configuration Option - Allow Add Test Case Version Relation ONLY on latest Test Case Version

Description

In order to have some coerence with related ticket.

// Because:
// The Relation must be frozen (cannot be deleted) when
// a new version of the test case is created.
//
// It seems confusing that relation can be added, then
// this new configuration will allow this operation
// only on latest test case version
//
$tlCfg->testcase_cfg->addTCVRelationsOnlyOnLatestTCVersion = TRUE;

20181216 - THIS SENTENCE has become WRONG
IMPORTANT NOTICE:
If you can NOT ADD, Also you can not delete an existent TC Relation that exists in an older TC Version

and the logic removed.

WHY ?
Because there is an config option that controls if TC Relations has to be FROZEN or NOT when a new TCVERSION is created

Tags

No tags attached.

Database (MySQL,Postgres,etc)

N/A

Browser

PHP Version

TestCaseID

QA Team - Task Workflow Status

READY FOR TESTING

Attached Files

Relationships

related to	0008466	resolved	fman	Configuration Option - Close/Freeze Test case version relations when creating a new test case version
child of	0008397	closed	fman	Availables hot-fixes for 1.9.18 & How To get full fixed package from GitHub

Notes
(0028229) fman (administrator) 2018-11-13 18:37	https://github.com/TestLinkOpenSourceTRMS/testlink-code/commit/2a45b8bd337b5ef7a358649ff6a7391b113ec2cc [^]

Issue History
Date Modified	Username	Field	Change
2018-11-13 18:35	fman	New Issue
2018-11-13 18:35	fman	Status	new => assigned
2018-11-13 18:35	fman	Assigned To	=> fman
2018-11-13 18:35	fman	Issue generated from: 0008466
2018-11-13 18:35	fman	Relationship added	related to 0008466
2018-11-13 18:35	fman	Fixed in Version	=> 1.9.19 (2019 Q1)
2018-11-13 18:35	fman	Relationship added	child of 0008397
2018-11-13 18:37	fman	Note Added: 0028229
2018-11-13 18:37	fman	Status	assigned => resolved
2018-11-13 18:37	fman	Resolution	open => fixed
2018-11-15 07:32	fman	Relationship added	related to 0008459
2018-12-16 13:25	fman	Description Updated	View Revisions
2018-12-16 15:34	fman	Description Updated	View Revisions