|Anonymous | Login | Signup for a new account||2020-02-21 07:30 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007278||TestLink||Bug Tracking System - Redmine Integration||public||2015-09-28 17:43||2018-11-24 09:00|
|Product Version||1.9.14 (2015 Q3)|
|Fixed in Version||1.9.16 (2016 Q4)|
|Summary||0007278: Customise Testlink Username to Equal Redmine Username|
|Description||Whenever a Bug is created from Testlink the 'Added by' field in Redmine always get populated with the API key name value stored in the Issue tracker management config.|
Also Assignee field is blank is Redmine.
1)Instead, would like to see the name of the user who executed the Test in Testlink to be appeared in Redmine against the "Added By' field.
2)Can we also pass Assignee name.
|Steps To Reproduce||1)Testlink is Integrated with Redmine Successfully.|
2)Testlink execute test case > fail > create issue
3)Bug created in redmine where bug fields have
"added by field" = "api key username" (Expected Same user name as testlink)
"assignee filed" = "blank" (Expected to pass a assignee name)
|Additional Information||Example: |
Testlink user : ABC (Failed test case)
Test link API User: XYZ (API KEY)
Actual : "ABC" failed the test case in testlink, bug created in Redmine with XYZ username.
Expected : ABC failed the test case in testlink, bug created in Redmine with ABC username.
|Tags||No tags attached.|
|QA Team - Task Workflow Status||READY FOR TESTING|
please first check if redmine API allows to set this values
IMHO is not ok set assigned to from testlink => will not implement
Redmine API reference i can find is only this, not sure what to do.
http://www.redmine.org/projects/redmine/wiki/Rest_api [^] (Read general topics)
Did not get your second statement on not ok set assigned to from testlink..??
Below is some more reference, basis which not sure what changes are to be done in testlink-redmine-api please help.
As of Redmine 2.2.0, you can impersonate user through the REST API by setting the X-Redmine-Switch-User header of your API request. It must be set to a user login (eg. X-Redmine-Switch-User: jsmith). This only works when using the API with an administrator account, this header will be ignored when using the API with a regular user account.
If the login specified with the X-Redmine-Switch-User header does not exist or is not active, you will receive a 412 error response.
>> This only works when using the API with an administrator account, this header >>will be ignored when using the API with a regular user account
this is IMHO not a solution.
>> Did not get your second statement on not ok set assigned to from testlink..??
Do not think is a good thing, you can assign task AFTER CREATE it (later) and this is not a drawback. This need too tight integration and this is not the idea
>>User name different in failed test case and bug created is a show stopper for us, I have got Redmine admin APIKEY with me so any solution ?
>>Agree on assign task user, its not a must have or show stopper.
>> User name different in failed test case and bug created is a show stopper for >> us, I have got Redmine admin APIKEY with me so any solution ?
This is an implementation that is critic just for you, then IMHO you have the code and you can implement it.
If you not I can do it but if your company does a donation (via paypal)
edited on: 2015-09-30 18:02
Do not have code please help, will support/donate.
|Any update ?|
|mail sent to address you have configured for your user.|
Checked internally did not get budget approval, i think i have to live with out this feature for now.
Hoping this feature in upcoming releases, Thanks.
|I'm sorry very much but I'm going to develop this only if someone will be willing to pay for the development.|
|2015-09-28 17:43||daki||New Issue|
|2015-09-28 18:26||fman||QA Team - Task Workflow Status||=> TBD|
|2015-09-28 18:26||fman||Severity||minor => feature request|
|2015-09-28 18:59||fman||Note Added: 0024054|
|2015-09-29 10:43||daki||Note Added: 0024058|
|2015-09-29 11:26||daki||Note Added: 0024059|
|2015-09-29 12:48||fman||Note Added: 0024060|
|2015-09-29 15:01||daki||Note Added: 0024061|
|2015-09-29 15:46||fman||Note Added: 0024062|
|2015-09-30 06:29||daki||Note Added: 0024067|
|2015-09-30 18:01||daki||Note Edited: 0024067||View Revisions|
|2015-09-30 18:02||daki||Note Edited: 0024067||View Revisions|
|2015-10-03 06:43||daki||Note Added: 0024077|
|2015-10-03 07:25||fman||Note Added: 0024078|
|2015-10-07 06:16||daki||Note Added: 0024099|
|2015-10-07 07:47||fman||Note Added: 0024100|
|2017-01-15 09:12||fman||Relationship added||related to 0007799|
|2017-01-15 09:12||fman||Fixed in Version||=> 1.9.16 (2016 Q4)|
|2017-01-15 09:12||fman||QA Team - Task Workflow Status||TBD => READY FOR TESTING|
|2017-01-15 09:12||fman||Status||new => resolved|
|2017-01-15 09:12||fman||Resolution||open => fixed|
|2017-01-15 09:12||fman||Assigned To||=> fman|
|2017-01-22 07:57||fman||Note Added: 0025863|
|2017-01-22 07:57||fman||Status||resolved => closed|
|2018-11-24 09:00||fman||Relationship added||related to 0008484|
|Copyright © 2000 - 2020 MantisBT Team|