Mantis Bugtracker 

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0006917TestLinkBug Tracking System - JIRA Integrationpublic2015-01-30 09:442015-02-06 19:04
Assigned To 
PrioritynormalSeverityfeature requestReproducibilityhave not tried
PlatformOSOS Version
Product Version1.9.12 (2014 Q3) 
Fixed in Version 
Summary0006917: Support Override JIRA config at test plan level
DescriptionSince we are using test plan for project level (means each test plan may be corresponding to a different JIRA project), it would be great to override the JIRA configuration at the test plan level, especially for projectkey, affectsVersions, customField, etc.

We are planning to use the TestLink custom fields to override the JIRA configurations.
To be better back compatible, we use the JIRA config field name as TestLink custom field name so it would be very easier to add any further customized fields in TestLink.

This won't be added into TestLink repo. It's put here for sharing purpose.
TagsNo tags attached.
Database (MySQL,Postgres,etc)MySQL
PHP Version
QA Team - Task Workflow StatusTBD
Attached Fileszip file icon [^] (22,752 bytes) 2015-01-30 09:44
jpg file icon TestPlanConfig.JPG [^] (51,511 bytes) 2015-01-30 09:44

jpg file icon CustomFieldConfig.JPG [^] (21,072 bytes) 2015-01-30 09:45

jpg file icon Custom Field Setting.JPG [^] (24,207 bytes) 2015-02-01 05:55

- Relationships

-  Notes
fman (administrator)
2015-01-31 08:12

Pay attention that with new implementation on 1.9.13 several attributes present on JIRA are presented on TESTLINK asking for this info to JIRA (affectedVersions, components, ecc)

It's obvious that projectkey is not one of this.
You idea can useful, but is you are working with a mapping 1 TESTLINK TESTPROJECT = 1 TEST PLAN, then you alreday have here a workaround.
create always a ONE TEST PROJECT for ONE TEST PLAN
fman (administrator)
2015-01-31 17:40

A good naming convention for custom fields is needed in other to try to create a generic solution.
swang3 (reporter)
2015-02-01 05:55

Change bugAdd.php (line 115, line 174-185) to allow it work with 0006920 to override configuration at TestPlan level.

User Guide:
1. You have to have a TestLink custom field named 'JIRA_Fields' set (screenshot attached).
2. Apply this field to your test project.
3. Override your JIRA configuration with JSON format string like this:
    "versions":[{"name":"[SI&T][Trunk Program]"}],
swang3 (reporter)
2015-02-01 06:11
edited on: 2015-02-01 06:12

I have to use test plan for project level because our projects have similar requirements/test cases which can be shared. Put them under the same TestLink Test Project would allow us to share test cases/requirements among them.

fman (administrator)
2015-02-01 18:32

>> Put them under the same TestLink Test Project would allow us to share test
>> cases/requirements among them.
You can also share test cases, using ghost feature.
You can have a test project with common test cases (consider it a MASTER LIBRARY) and use it on different test projects.
Same for requirements using links.

This approach requires a little bit more work, because you have to create a test case in each test project to use the ghost.
swang3 (reporter)
2015-02-02 05:29

Thanks, ghost string is very useful for sharing test steps, but not for test case sharing as you stated "This approach requires a little bit more work":)

- Issue History
Date Modified Username Field Change
2015-01-30 09:44 swang3 New Issue
2015-01-30 09:44 swang3 File Added:
2015-01-30 09:44 swang3 File Added: TestPlanConfig.JPG
2015-01-30 09:45 swang3 File Added: CustomFieldConfig.JPG
2015-01-31 08:12 fman Note Added: 0022590
2015-01-31 17:37 fman Note View State: 0022590: public
2015-01-31 17:40 fman Note Added: 0022601
2015-02-01 05:55 swang3 Note Added: 0022605
2015-02-01 05:55 swang3 File Added: Custom Field Setting.JPG
2015-02-01 06:11 swang3 Note Added: 0022606
2015-02-01 06:12 swang3 Note Edited: 0022606 View Revisions
2015-02-01 18:32 fman Note Added: 0022614
2015-02-02 05:29 swang3 Note Added: 0022616
2015-02-06 19:04 fman QA Team - Task Workflow Status => TBD

Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker