MantisBT - TestLink
View Issue Details
0008180TestLinkBug Tracking System - Redmine Integrationpublic2018-01-16 10:502018-04-14 09:04
kostgr_2 
fman 
normalfeature requestN/A
closedfixed 
1.9.16 (2016 Q4) 
1.9.17 (2018 Q1) 
everyone
READY FOR TESTING
0008180: Support dynamic values in the custom fields for Redmine for issue creation
We would like to use some custom fields in redmine for some test case execution informations: build, platform etc.

The feature http://forum.testlink.org/viewtopic.php?f=55&t=7779 [^] allows us to use redmine issue description field for that, but it is not so good for reporting/analysing etc.

Our idea is to use the same placeholders as in the mentioned feature description from for forum with some more placeholders for values without labels:
'%%EXECID_VAL%%', '%%TESTER_VAL%%','%%TESTPLAN_VAL%%','%%PLATFORM_VAL%%',
'%%BUILD_VAL%%', '%%EXECTS_VAL%%','%%EXECSTATUS_VAL%%'.

In the static configuration section for custom fields of redmine the mentions placeholders can be used for values.

So we get our test case execution properties automatically into redmine at the issue creation.
Sample configuration for redmine custom fields on testlink side:

  <custom_fields type="array">
   <custom_field id="19" name="Testlink Build">
     <value>%%BUILD_VAL%%</value>
  </custom_field>
  </custom_fields>
Implemented in two commits:
https://github.com/kostgr/testlink-code/commit/9649093673613f60a29cfc2248b70d9ec12e770e [^]

and then
https://github.com/kostgr/testlink-code/commit/433330699bdcd789c9c44dd56b798cc25a51e221 [^]

The first commit unfortunately is combined with another feature (always adding two links to TestLink at creating issue in bugtracking system instead of one - direct link to execution report was added in addition to the link to test case execution)
No tags attached.
related to 0006864closed fman Create Issue WHILE Executing - possibility to provide issue description 
child of 0007817closed fman Availables hot-fixes for 1.9.16 & How To get full fixed package from GitHub 
Issue History
2018-01-16 10:50kostgr_2New Issue
2018-01-16 23:15fmanNote Added: 0027155
2018-01-17 07:31kostgr_2Note Added: 0027160
2018-01-17 07:31kostgr_2Note Edited: 0027160bug_revision_view_page.php?bugnote_id=27160#r5416
2018-01-17 09:44fmanNote Added: 0027161
2018-01-20 19:08fmanRelationship addedrelated to 0006864
2018-01-20 20:28fmanNote Added: 0027164
2018-01-20 20:28fmanAssigned To => fman
2018-01-20 20:28fmanStatusnew => work in progress
2018-01-20 20:28fmanQA Team - Task Workflow Status => TBD
2018-01-20 20:28fmanProduct Version => 1.9.16 (2016 Q4)
2018-02-24 15:42fmanStatuswork in progress => assigned
2018-02-24 15:42fmanQA Team - Task Workflow StatusTBD => READY FOR TESTING
2018-02-24 15:42fmanStatusassigned => resolved
2018-02-24 15:42fmanFixed in Version => 1.9.17 (2018 Q1)
2018-02-24 15:42fmanResolutionopen => fixed
2018-02-24 15:43fmanRelationship addedchild of 0007817
2018-04-14 09:04fmanNote Added: 0027298
2018-04-14 09:04fmanStatusresolved => closed

Notes
(0027155)
fman   
2018-01-16 23:15   
Please provide clear distinct PULL REQUEST, in order to allow a CLEAR HISTORY of commits on the base code LOG.
I do not think that will be a lot difficult for you

Thanks a lot
(0027160)
kostgr_2   
2018-01-17 07:31   
For someone experienced with git its not as hard to use the infos. I have to find time to do extra work.
The issue here is that our commits have to be splitted and that some of changes are based on the other ones. I had to reimplement the changes to split them correctly. It tooks time and brings no gain for us. If you would want to accept both changes, than it would be much easier. Otherwise the separate pull requests would also conflict with one another.

(0027161)
fman   
2018-01-17 09:44   
>> For someone experienced with git its not as hard to use the infos. I have to find time to do extra work.

Ok, I understand you do not want to help more than this, but next time think about using a better workflow that will made integration easier.
(0027164)
fman   
2018-01-20 20:28   
Refactored:

Same keys used for replacement on notes (original implementation), and for Custom Fields for Redmine, except EXECNOTES

Need to be tested
(0027298)
fman   
2018-04-14 09:04   
release 1.9.17