|Anonymous | Login | Signup for a new account||2020-04-06 12:30 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005663||TestLink||Bug Tracking System - JIRA Integration||public||2013-04-26 11:53||2013-05-22 20:56|
|Product Version||1.9.6 (2013 Q1 - bug fixing)|
|Fixed in Version||1.9.7 (2013 Q2 - bug fixing)|
|Summary||0005663: Manage the fields thate are filled in the Jira issue and the data in them|
|Description||Provide a way (or a least a tutorital how to make changes in the code) to manage the data filled in the fields of the created Jira issue e.g. to fill the build as an Affected version, the user who executed the test as Reporter (because the SOAP configuration keeps the password in plain text and it's not a safe option).|
Also give explanation about the id-s of the attributes and components needed in the configuration xml, because it's not clear what exactly to do with them.
|Additional Information||I already tried some changes in the code but nothing worked.|
|Tags||No tags attached.|
|QA Team - Task Workflow Status||READY FOR TESTING|
edited on: 2013-04-26 13:23
>> the user who executed the test as Reporter
IMHO this neither critic nor important.
>> Also give explanation about the id-s of the attributes and components needed >> in the configuration xml, because it's not clear what exactly to do with them.
unfortunately this request is far from clear.
You have to ask in a very,very detailed way in order to have any chance to recieve a answer.
I can not provide a tutorial to make changes to code, changes to be done are not hard to do, if you do some debug on code.
I've provided basic integration and because I'm not a JIRA user, i think more info can be produced by people like you that use JIRA everyday.
IMHO issue creation from TestLink has to be viewed as creation of a Draft o Blue print of issue, that will need manual rework on the right tool i.e. the bug tracking system.
In the XML CFG that you got when doing the config, IMHO there is all
info you need alt least to provide other issue attributes.
You can use forum www.teamst.org to contact other real world JIRA users.
'Please provide ...' , or ' It would be great if ..', is IMHO a lot better than 'Provide ...'
You can manage by yourself all information you want without any development if you choose instead of CREATE ISSUE, the LINK ISSUE OPTION.
This way you can access to JIRA and using JIRA GUI provide all info.
Only drawback: you need to provide manually the JIRA ID to TestLink
|no more user feedback|
|2013-04-26 11:53||Lucy||New Issue|
|2013-04-26 13:05||fman||Priority||high => normal|
|2013-04-26 13:11||fman||Note Added: 0018783|
|2013-04-26 13:13||fman||Note Edited: 0018783||View Revisions|
|2013-04-26 13:22||fman||Note Edited: 0018783||View Revisions|
|2013-04-26 13:22||fman||Note View State: 0018783: public|
|2013-04-26 13:23||fman||Note Edited: 0018783||View Revisions|
|2013-04-28 08:46||fman||Note Added: 0018792|
|2013-05-06 18:35||fman||QA Team - Task Workflow Status||TBD => READY FOR TESTING|
|2013-05-06 18:35||fman||Note Added: 0018890|
|2013-05-06 18:35||fman||Status||new => resolved|
|2013-05-06 18:35||fman||Fixed in Version||=> 1.9.7 (2013 Q2 - bug fixing)|
|2013-05-06 18:35||fman||Resolution||open => fixed|
|2013-05-06 18:35||fman||Assigned To||=> fman|
|2013-05-22 20:56||fman||Status||resolved => closed|
|Copyright © 2000 - 2020 MantisBT Team|