|Anonymous | Login | Signup for a new account||2018-12-17 01:39 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008184||TestLink||Bug Tracking Systems Integration||public||2018-01-16 12:05||2018-04-14 09:04|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Product Version||1.9.17 (2018 Q1)|
|Fixed in Version||1.9.17 (2018 Q1)|
|Summary||0008184: Issue on test case STEP - Issue summary configuration|
|Description||The default issue summary on the issues created on the step level is pretty confusing:|
Issue executing step number 5.
Some of our testers have created such a tickets in redmine. On a step level there is no possibility to add direct link to test case execution and the test case is not referenced appropriately. So such an issues are useless in redmine.
The reason for such a default is small bug in the issue text generation code.
See fixing-commit https://github.com/kostgr/testlink-code/commit/520db481e8bff90a09780fef91bbe9fae166b755 [^]
|Steps To Reproduce||1. Configure Issue Tracking integration (for redmine)|
2. Create issue on some test case step from the test case execution view.
|Tags||No tags attached.|
|QA Team - Task Workflow Status||TBD|
|Unfortunately I found your issue report not detailed as needed, then please provide example instead of sentences like 'the test case is not referenced appropriately.'|
Issue created in redmine from step has from default only that informations:
"Issue executing step number X" nothing else. No Testlink project, no platform, no build, no test case. What should one do with this issue?
One of our testers has made some of such issues. We had to review each issue from testlink and add at least the links to the test case executions to be able to process such a ticket.
It should actually be "Issue executing step numer X TT-123 Test creating new address entry", where TT-123 - is the unique number of the test case from Testlink and "Test creating new address entry" is the title of the test case.
|1. Issue subject can be edited => proposal can be not good, but issue focus changes|
Added possibility to configure subject at test case step level
ALL THESE IS SUPPORTED NOW
'$$issue_on_step %%STEPNUMBER%% - $$issue_subject_tcname %%TCNAME%% - ' .
'$$issue_subject_projectname %%PROJECTNAME%% - ' .
'$$issue_subject_planname %%PLANNAME%% - ' .
'$$issue_subject_buildname %%BUILDNAME%% - ' .
$tlCfg->exec_cfg->issues->tcstep_level->subject = '$$issue_on_step %%STEPNUMBER%% - $$issue_subject_tcname %%TCNAME%% ';
|2018-01-16 12:05||kostgr_2||New Issue|
|2018-01-16 22:57||fman||Note Added: 0027152|
|2018-01-16 22:57||fman||Assigned To||=> fman|
|2018-01-16 22:57||fman||Status||new => feedback|
|2018-01-17 07:26||kostgr_2||Note Added: 0027158|
|2018-01-17 07:26||kostgr_2||Status||feedback => assigned|
|2018-02-24 16:30||fman||Note Added: 0027238|
|2018-02-24 17:55||fman||Note Added: 0027239|
|2018-02-24 17:55||fman||QA Team - Task Workflow Status||=> TBD|
|2018-02-24 17:55||fman||Status||assigned => resolved|
|2018-02-24 17:55||fman||Fixed in Version||=> 1.9.17 (2018 Q1)|
|2018-02-24 17:55||fman||Resolution||open => fixed|
|2018-02-24 17:58||fman||Product Version||=> 1.9.17 (2018 Q1)|
|2018-02-24 17:58||fman||Relationship added||child of 0007817|
|2018-02-24 17:59||fman||Summary||Issue summary is confusing at creating Bug Tracking issue on test case step level => Issue on test case STEP - Issue summary configuration|
|2018-02-25 13:36||fman||Issue cloned: 0008211|
|2018-02-25 13:36||fman||Relationship added||related to 0008211|
|2018-04-14 09:04||fman||Note Added: 0027297|
|2018-04-14 09:04||fman||Status||resolved => closed|
|Copyright © 2000 - 2018 MantisBT Team|