|Anonymous | Login | Signup for a new account||2019-02-16 14:20 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007929||TestLink||Bug Tracking System - JIRA Integration||public||2017-04-26 09:37||2018-04-14 09:04|
|Product Version||1.9.16 (2016 Q4)|
|Fixed in Version||1.9.17 (2018 Q1)|
|Summary||0007929: Create issue from testlink use wrong username: integration user instead current user|
|Description||We upgrade testlink from 1.9.4 to 1.9.16.|
And find this issue:
When create a bug from testlink, reporter/note added user is not the current user.
I checked the changelog and find an issue discussed before:
We got the same problem now.
|Steps To Reproduce||Create issue or add note from the test exec page ---- snap1.png|
Use current user to report bug/add note.
|Tags||No tags attached.|
|QA Team - Task Workflow Status||READY FOR TESTING|
|Attached Files|| snap1.png [^] (17,040 bytes) 2017-04-26 09:37
snap2.png [^] (57,388 bytes) 2017-04-26 09:37
snap3.png [^] (20,739 bytes) 2017-04-27 01:40
snap4.png [^] (23,946 bytes) 2017-04-27 02:46
details about user config on JIRA and testlink are needed.
Have you tried with our test installation of JIRA on Cloud?
Add snap3.png to provide testlink config.
For jira config, I am not sure which info should provide. Would you describe more clear?
Jira version: Atlassian JIRA Project Management Software (v7.1.9#71013-sha1:1aa0586)
|I will tried the cloud JIRA and get back soon.|
I tried to use my own atlassian ID to log in to testlink.atlassian.net.
Receive hint showed in snap4.png.
edited on: 2017-04-27 05:00
you can not use your atlassian login because is not configured.
I'm going to add it
>> For jira config, I am not sure which info should provide. Would you describe more clear?
excuse me, if you do not understand how to configure, how you are testing this ?
Please provide minimum detail of how users have been configured on testlink and on jira
We use a third sso system to do all the system(testlink, mantis, jira, svn, etc.) authoration. So I may not try your cloud jira.
I am not the administrator of Jira. So I don't know the exact config.
And I don't think there's anything special.
It just work fine before we upgrade from 1.9.4 to 1.9.16.
I'm sorry but this
>>So I may not try your cloud jira.
This is not really true, because if you set a testlink sandbox you can do the test I've indicated
>> I am not the administrator of Jira. So I don't know the exact config.
>> And I don't think there's anything special.
IMHO you need to really check how things are configured.
>> It just work fine before we upgrade from 1.9.4 to 1.9.16.
As explained I can only do tests on my cloud installation, if they are ok, and you are not able to provide detailed information, I'm not able to help.
on related ticket there are several pointers to information, try to give a look to understand if they can provide you help.
Unfortunately I can not do anything else for you.
Hi, we did a lot test today, and here's the result:
1. test jira api, to confirm it could be properly receive and set reporter. --- test pass.
2. check the jira permission config, to confirm tuser(used to connect to jira from testlink) could modify Reporter. ---- test pass
3. modify jirarestinterface.class.php, set reporter to a static value, to confirm if jira issue reporter could be changed by testlink --- test pass
Still working on more test to confirm where is wrong......
Thanks for your update. it seems there is a little glitch when jirarestinterface.class.php receive this info.
hope you will find it
edited on: 2017-05-16 13:56
4. test jira api, to confirm createMeta worked fine --- test pass
5. check if testlink receive json data of createMeta from jira --- test pass
So we guess something wrong when parsing the json data.
$ret[$ele->key][$it->id]['fields'][$field->key] = $field->key;
$field->key should be $field->name
$setReporter = isset($issueFields[$issueType]['reporter']
$setReporter = isset($issueFields[$issueType]['fields']['Reporter']
We changed this and it worked fine now.
We still have another problem:
When add a comment, author could not change to the proper user.
Have not check and analyze yet.
|Thanks for your help|
>> When add a comment, author could not change to the proper user.
|2017-04-26 09:37||apronwq||New Issue|
|2017-04-26 09:37||apronwq||File Added: snap1.png|
|2017-04-26 09:37||apronwq||File Added: snap2.png|
|2017-04-26 12:14||fman||Note Added: 0026310|
|2017-04-26 18:53||fman||Assigned To||=> fman|
|2017-04-26 18:53||fman||Status||new => feedback|
|2017-04-27 01:40||apronwq||Note Added: 0026319|
|2017-04-27 01:40||apronwq||Status||feedback => assigned|
|2017-04-27 01:40||apronwq||File Added: snap3.png|
|2017-04-27 01:42||apronwq||Note Added: 0026320|
|2017-04-27 02:46||apronwq||Note Added: 0026321|
|2017-04-27 02:46||apronwq||File Added: snap4.png|
|2017-04-27 04:50||fman||Note Added: 0026322|
|2017-04-27 04:51||fman||Note Edited: 0026322||View Revisions|
|2017-04-27 04:53||fman||Note Edited: 0026322||View Revisions|
|2017-04-27 05:00||fman||Note Edited: 0026322||View Revisions|
|2017-04-27 05:01||fman||Status||assigned => feedback|
|2017-05-01 07:36||apronwq||Note Added: 0026330|
|2017-05-01 07:36||apronwq||Status||feedback => assigned|
|2017-05-01 09:22||fman||Relationship added||related to 0007757|
|2017-05-01 09:26||fman||Note Added: 0026331|
|2017-05-01 09:26||fman||Status||assigned => feedback|
|2017-05-01 09:32||fman||Relationship added||related to 0006513|
|2017-05-01 09:39||fman||Note Added: 0026332|
|2017-05-10 14:09||apronwq||Note Added: 0026343|
|2017-05-10 14:09||apronwq||Status||feedback => assigned|
|2017-05-10 14:26||fman||Note Added: 0026344|
|2017-05-16 13:48||apronwq||Note Added: 0026367|
|2017-05-16 13:50||apronwq||Note Added: 0026368|
|2017-05-16 13:55||apronwq||Note Edited: 0026367||View Revisions|
|2017-05-16 13:56||apronwq||Note Edited: 0026367||View Revisions|
|2017-05-16 14:20||fman||Note Added: 0026369|
|2017-05-16 18:31||fman||Note Added: 0026372|
|2017-05-16 18:34||fman||QA Team - Task Workflow Status||=> READY FOR TESTING|
|2017-05-16 18:34||fman||Status||assigned => resolved|
|2017-05-16 18:34||fman||Fixed in Version||=> 1.9.17 (2018 Q1)|
|2017-05-16 18:34||fman||Resolution||open => fixed|
|2017-05-16 18:39||fman||Note Added: 0026373|
|2017-05-29 18:45||fman||Relationship added||has duplicate 0007950|
|2018-04-14 09:04||fman||Note Added: 0027329|
|2018-04-14 09:04||fman||Status||resolved => closed|
|Copyright © 2000 - 2019 MantisBT Team|