Mantis Bugtracker          
testlink.org

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0007511TestLinkNew Featurepublic2016-04-21 13:162016-06-30 13:34
Reporterdorusinec 
Assigned To 
PrioritynormalSeverityfeature requestReproducibilityalways
StatusnewResolutionreopened 
PlatformOSOS Version
Product Version 
Fixed in Version 
Summary0007511: Possibility to easily change platform for Test Cases while assigned testers remains the same
DescriptionPossibility to easily change platform for Test Cases while assigned testers remains the same.
TagsNo tags attached.
Database (MySQL,Postgres,etc)MySQL
Browser
PHP Version
TestCaseID
QA Team - Task Workflow StatusTBD
Attached Files

- Relationships

-  Notes
(0024724)
fman (administrator)
2016-04-21 16:25

dear user
your requirement is not completely detailed, no steps to reproduce are provided.
In addition easily means nothing

Please if provide better requirements in order to have any chance your request will be evaluated

ALSO testlink version is a MUST
(0024731)
dorusinec (reporter)
2016-04-22 06:07

Testlink version would be mandatory then: 1.9.10

Steps to reproduce will be provided.
(0024732)
fman (administrator)
2016-04-22 06:09

1.9.10 is not supported anymore => you need to confirm that issue is present in 1.9.14 otherwise issue will be closed
(0024739)
ansar (reporter)
2016-04-22 18:23

I believe what he is asking is an easier way to create new platforms and have the ability to assign test cases and testers from an existing platform to the new platform. Let me see if I can list out the steps.

1. Create Platform1 and assign Test Cases and Testers.
2. Create Platform2, which will be a similar platform to Platform1.
3. Notice that you have to manually add Test Cases and Testers to Platform2.

It would be nice to be able to create a new Platform and have the ability to select an existing Platform for Test Cases, Tester Assignment, and Priority.
(0024740)
fman (administrator)
2016-04-23 07:02
edited on: 2016-04-23 07:22

@ansar
Please do not try to translate an other user request, I do not like this kind of approach.
He/she is responsible for his/her request.

If you have a request then open a new issue.
I'm going to delete your note after you have created a new clear feature request.

(0024752)
fman (administrator)
2016-04-25 09:25

waiting for steps
(0024757)
ansar (reporter)
2016-04-25 14:14

Will do fman. Let me get my notes together and I will submit a feature request. We currently do this on the backend in the database, but it would be nice to have it done through the interface as well. :)
(0024761)
fman (administrator)
2016-04-28 13:32

no more user information
(0024797)
dorusinec (reporter)
2016-05-12 12:37

present also in 1.9.14

1. Assign some Test Cases to Platform1 as well Tester1.
2. Now I realize that I made a mistake and it should be Platform2.
3. I‘d like to make a bulk change and reassign the Test Cases to Platform2 (while Tester1 remains assigned) but the only way is to do it manually.
(0024808)
fman (administrator)
2016-05-12 18:32

still steps to reproduce are not enough, makeing working on this impossible.
Can you be kindly enough to go to forum and read examples and documentation regarding how report issues in an effective way ?
(0024819)
dorusinec (reporter)
2016-05-13 12:42

Preconditions:
Platforms (Platform1, Platform2), dozens of test cases and users created (User1, User2).

Steps to reproduce:
1. Click Add / remove test cases link in Desktop.
2. Select all test cases and add them to the both platforms.
3. Click Assign test case execution link.
4. In the window, choose Platform1 in Setting part.
5. Now select desired test cases and assign them to User1.
6. Test cases are assigned to Platform1 and User1.

Now I need to re-plan my testing and change the platform – from Platform1 to Platform2.

1. Click Assign test case execution link.
2. In the window, choose Platform2.
3. Now you need to select the same test cases once again and assign them to User1.

This is time-consuming activity if you have to re-assign too many test cases. It would be nice to do this in a bulk way, e.g. having some controls allowing users to easily change the platform. First, you will filter test cases assigned to Platform1 and User1. Then, there will be controls similar to Bulk user assignment (Do Bulk user remove) functionality to do bulk change of platform.
(0024821)
fman (administrator)
2016-05-13 15:04

>> having some controls allowing users to easily change the platform.
this kind of requirement is absolutely useless, because said nothing.
Is this the kind of req you accept from your customers?
(0024823)
ansar (reporter)
2016-05-13 16:41

dorusinec, I currently do what you want with database updates in the backend. I am in the process of testing it again with TestLink 1.9.14, since we have not updated the platforms since TestLink 1.9.12.

I have been busy and on vacation for a week, so I apologize for not responding sooner.
(0025053)
dorusinec (reporter)
2016-06-30 13:27

>>this kind of requirement is absolutely useless, because said nothing.
I proposed a way how you can do that "First, you will filter test cases assigned to Platform1 and User1. Then, there will be controls similar to Bulk user assignment (Do Bulk user remove) functionality to do bulk change of platform".

I would expect that the implementation of my feature request is upon you and guys developing TL.

Do not you still understand my request or where is the problem?
(0025056)
fman (administrator)
2016-06-30 13:34

>> I would expect that the implementation of my feature request is upon you and >> guys developing TL.
IMHO you need to understand that feature requests are not automatically developed just because has been reported.
It's dev team choice (my choice) to implement or not.
You have provided no more info for more than a month, and still from my point of view requirement is not enough to evalute.

- Issue History
Date Modified Username Field Change
2016-04-21 13:16 dorusinec New Issue
2016-04-21 16:25 fman Note Added: 0024724
2016-04-21 16:25 fman Status new => feedback
2016-04-22 06:07 dorusinec Note Added: 0024731
2016-04-22 06:07 dorusinec Status feedback => new
2016-04-22 06:09 fman Note Added: 0024732
2016-04-22 18:23 ansar Note Added: 0024739
2016-04-23 07:02 fman Note Added: 0024740
2016-04-23 07:22 fman Note Edited: 0024740 View Revisions
2016-04-25 09:25 fman Note Added: 0024752
2016-04-25 09:25 fman Assigned To => fman
2016-04-25 09:25 fman Status new => feedback
2016-04-25 14:14 ansar Note Added: 0024757
2016-04-28 13:32 fman QA Team - Task Workflow Status => TBD
2016-04-28 13:32 fman Note Added: 0024761
2016-04-28 13:32 fman Status feedback => closed
2016-04-28 13:32 fman Resolution open => unable to reproduce
2016-05-12 12:37 dorusinec Note Added: 0024797
2016-05-12 12:37 dorusinec Status closed => assigned
2016-05-12 12:37 dorusinec Resolution unable to reproduce => reopened
2016-05-12 18:32 fman Note Added: 0024808
2016-05-12 18:32 fman Assigned To fman =>
2016-05-12 18:32 fman Status assigned => feedback
2016-05-13 12:42 dorusinec Note Added: 0024819
2016-05-13 12:42 dorusinec Status feedback => new
2016-05-13 15:04 fman Note Added: 0024821
2016-05-13 16:41 ansar Note Added: 0024823
2016-06-30 13:27 dorusinec Note Added: 0025053
2016-06-30 13:34 fman Note Added: 0025056



Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker