|Anonymous | Login | Signup for a new account||2018-10-16 21:56 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008389||TestLink||Requirement Management||public||2018-09-28 04:53||2018-09-28 07:05|
|Platform||Linux||OS||CentOS Linux 7||OS Version||3.10.0-862.11.6|
|Product Version||1.9.17 (2018 Q1)|
|Fixed in Version|
|Summary||0008389: Link Requirement Specification to JIRA User Story|
|Description||Upon Req. Spec. is created on TestLink from specific project, I do not see any option available which could link it with JIRA user story.|
Do this testlink version included user story management connecting to JIRA?
|Steps To Reproduce||1. Login to TestLink account.|
2. Select your test project.
3. Enter into Requirement Specification from home page.
4. Click 'Create' to generate Requirement Specification Operations.
5. Click Settings icon from req. spec. operations, and then click "Create" to generate Requirement Operations.
6. Click the desired req. operations to open up requirements.
There is no option under "Relations" section to link JIRA user story.
|Tags||No tags attached.|
|Database (MySQL,Postgres,etc)||MySQL Ver 5.7.23 for linux-glibc2.12 on x86_6|
|Browser||Firefox Quantum 62.0 (64-bit)|
|PHP Version||PHP 7.0.31 (cli)|
|QA Team - Task Workflow Status||TBD|
If you do not found any issue/CR here or something in the documentation, this means feature does not exists.
Right now only integration with Ticket/Bug Systems is available.
An errort was started in the past to create a similar interface with Management Systems like JAMA Software but never completed and right now is not in the roadmap
edited on: 2018-09-28 06:24
What I think that we could use back the Issue Tracker Management feature, and then add it into requirement specification, say, under Relations section should be enough to achieve this criteria, with that "Linked Existent Issue" icon make it available in Relations section.
Your explanation needs more detailed information.
Several architecture changes will be needed to do not creata a 'Quick & TOO DIRTY' solution
Anyway: FORK, develop & contribute if you want
|2018-09-28 04:53||kengseng||New Issue|
|2018-09-28 05:55||fman||QA Team - Task Workflow Status||=> TBD|
|2018-09-28 05:55||fman||Priority||high => normal|
|2018-09-28 05:55||fman||Severity||major => feature request|
|2018-09-28 05:58||fman||Note Added: 0027901|
|2018-09-28 06:23||kengseng||Note Added: 0027902|
|2018-09-28 06:24||kengseng||Note Edited: 0027902||View Revisions|
|2018-09-28 06:37||fman||Note Added: 0027903|
|2018-09-28 07:05||kengseng||Note Added: 0027904|
|Copyright © 2000 - 2018 MantisBT Team|