Updated Version page

[oskarhurst]

Is your feature request related to a problem? Please describe.
When creating a new version of a product, inorder for a user to clone all the test plans and move them to the new versions they have to manually select each test plan one at a time and clone it. This can be very time consuming when there are 50 test plans or more.

Describe the solution you'd like
I was hoping to open up a new PR with a new Version page which duplicates the behavior of the testplan page where it lists all the test cases which you can then select andd to a multi testplan clone of all of them at once. I am looking fior advice on out and can proceed in making this.

Additional context
There are multiple ways to achieve this. Which of the methods would be most advised. Currectly the versions can be found within the admin section of the website and are generated using the defualt AdminModel class. From this list when you select a specific version it directs you to the default admin changeform page.

1. The first method would be extent this changeform page and add in the testplan lists and clone functionality found in the testplan page.
2. Second method is to create a new version page which copies the full style of the testplan page but for version information. when selecting the version from the admin version list it would redirect to this page, and from this page you can be directed to the changeform page.
3. Third, Within the search tab include a new search for version page. which from there you can then be redirected to a new version page also copying the behavior of the test plan page.

@atodorov

[atodorov]

Describe the solution you'd like I was hoping to open up a new PR with a new Version page which duplicates the behavior of the testplan page where it lists all the test cases which you can then select andd to a multi testplan clone of all of them at once. I am looking fior advice on out and can proceed in making this.

It sounds like what you need is for the TP cloning page to be able to clone multiple objects, not just one. (and as part of the editing step you can select your new Version or whatever else for that matter).

Similar to when you select multiple TCs inside a TP and click the Clone item from the hamburger menu:
https://public.tenant.kiwitcms.org/cases/clone/?c=14797&c=15555

Then basically replicate all of the input fields for each of the chosen TPs.

3. Third, Within the search tab include a new search for version page. which from there you can then be redirected to a new version page also copying the behavior of the test plan page.

To me this sounds more like "On the Search Test Plans page add a button/menu which will trigger the multi-tp-clone URL". This sounds more like an additional usability functionality.

So your workflow would become: Filter all TPs based on Product/Version combo, select all/some and Clone.

I'm not quite sure how this should be implemented. Probably something like this:

1. Allow TP clone page to accept multiple arguments via query string. The PK specified in the URL could be "1st object" and then the rest could be extra.

2. Refactor the cloning code to accept an iterator of objects and loop over them

3. Iron out forms for selecting different names/products/versions for the new objects which are about to be created

4. Work on the usability part on the Search Test Plans page.

Probably start sending some PRs to see how initial implementation looks like and we can take it from there.

[oskarhurst]

Describe the solution you'd like I was hoping to open up a new PR with a new Version page which duplicates the behavior of the testplan page where it lists all the test cases which you can then select andd to a multi testplan clone of all of them at once. I am looking fior advice on out and can proceed in making this.

It sounds like what you need is for the TP cloning page to be able to clone multiple objects, not just one. (and as part of the editing step you can select your new Version or whatever else for that matter).

Similar to when you select multiple TCs inside a TP and click the Clone item from the hamburger menu: https://public.tenant.kiwitcms.org/cases/clone/?c=14797&c=15555

Then basically replicate all of the input fields for each of the chosen TPs.

3. Third, Within the search tab include a new search for version page. which from there you can then be redirected to a new version page also copying the behavior of the test plan page.

To me this sounds more like "On the Search Test Plans page add a button/menu which will trigger the multi-tp-clone URL". This sounds more like an additional usability functionality.

So your workflow would become: Filter all TPs based on Product/Version combo, select all/some and Clone.

I'm not quite sure how this should be implemented. Probably something like this:

1. Allow TP clone page to accept multiple arguments via query string. The PK specified in the URL could be "1st object" and then the rest could be extra.
2. Refactor the cloning code to accept an iterator of objects and loop over them
3. Iron out forms for selecting different names/products/versions for the new objects which are about to be created
4. Work on the usability part on the Search Test Plans page.

Probably start sending some PRs to see how initial implementation looks like and we can take it from there.
A.

B.

Is it possible to adapt table B. from the testplans search page to have the check box options from table A.
or do you think it would be more advised to adapt the list from table A. to display the same information and work with filtering objects as table b.

[atodorov]

Is it possible to adapt table B. from the testplans search page to have the check box options from table A.

It is. In fact this table already has the checkbox widget in the left-most column (but it is hidden in the majority of cases, see source code) so what it is missing is an action button to initiate the cloning operation.

or do you think it would be more advised to adapt the list from table A. to display the same information and work with filtering objects as table b.

^^^ this sounds like going into the wrong direction but you are welcome to experiment if you want.

However what you describe in this last comment is the final step of the puzzle (although I guess it can be implemented first to make developing the rest easier).