0008286: Requirements Filtering: Invalid behaviour

testlink.org

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0008286

TestLink

Requirement Management

public

2018-06-08 09:55

2018-06-08 13:23

Reporter

abIng

Assigned To

Priority

normal

Severity

feature request

Reproducibility

always

Status

new

Resolution

open

Platform

OS Version

Product Version

1.9.17 (2018 Q1)

Fixed in Version

Summary

0008286: Requirements Filtering: Invalid behaviour

Description

When filtering the requirements the search is performed on all versions/revisions of requirement. Should be : only the current version.

The sample database exported is attached. See the project AB3.

The problem is demonstrated on the screen capture.
Here the requirements are filtered according to the status = Obsolete.

The requirement REQ1 is present in the result. However its current status is Finished (the current version is 3).
This requirement is filtered since its status in version 2 is Obsolete, see at the bottom of the screen.

The expected behaviour is to filter the requirements that have the Status=Obsolete for the most recent version.

Steps To Reproduce

The project AB3 contains 3 requirements:
- REQ1:
  - version 3: Status = Finish
  - version 2: Status = Obsolete
  - version 1: Status = Draft
- REQ2
  - version 1: Status =Obsolete
- REQ3
  - version 1: Status = Draft

Filter on Obsolete returns REQ1 and REQ2.
Should be: REQ2 only

Filter on Draft - REQ1 and REQ3 are returned
Should be : REQ3 only

Additional Information

The filters in test specifications and in requirement specifications are implemented in different ways:
- for tests only the current versions are scanned
- for requirements all versions are searched

The implementation for tests is more natural

Tags

No tags attached.

Database (MySQL,Postgres,etc)

any (tested on MySQL and MS SQL)

Browser

PHP Version

TestCaseID

QA Team - Task Workflow Status

TBD

Attached Files

logpng.7z [^] (73,301 bytes) 2018-06-08 09:55

Relationships

Notes
(0027558) fman (administrator) 2018-06-08 13:22	Try to give issues a summary with some meaning, and not what you have done with this. This is NOT AN ISSUE but a Change Request on behaivour

Issue History
Date Modified	Username	Field	Change
2018-06-08 09:55	abIng	New Issue
2018-06-08 09:55	abIng	File Added: logpng.7z
2018-06-08 13:22	fman	Note Added: 0027558
2018-06-08 13:23	fman	QA Team - Task Workflow Status	=> TBD
2018-06-08 13:23	fman	Severity	major => feature request
2018-06-08 13:23	fman	Category	Filters => Requirement Management