I have tested this item ✅ successfully on c503b03

Easy to get into a muddle but works as described.

Thanks a lot for working on this issue! Unfortunately I am not in favour of this implementation, from UX point of view.
Batch copy and move is not quite easy to understand, but at least the process should be everywhere the same. Behavoiur must be predictable.
Would it be possible to implement this behaviour "as always"?

Always:

user selects an item in the list and activates the batch button
(the system has the ids of the selected items)

on the modal: the users selects a target for his copy or move from the dropdown

decides if the action copy or move is to be performed.

your implementation

user selects an item in the list and activates the batch button (as he uses to do in other places)
(the system ignores the selection)

The "keep original tag" is misleading. The user's selection in the list is ignored, he must select the items now in the dropdown list.

After the selection of an item from the list, the select is replaced by another question. This change is so fast and the texts look similiar that it is difficult to notice the replacement. The user could think that he still sees his selection.

It would be clearer if the new block is appended to the first one.

The process then works like a charm.

I think that this causes confusion

In my opinion, the process should be the same in all categories and all other components, then it does not need extra documentation.

@chmst isnt this identical to the ui for batch copying and moving menu items??

@brianteeman not if I understand this correctly

You choose a menuitem in the list (the systems holds the id), opens the batch modal

then you choose a target menuitem and decides if you want a copy or move.

You must not do this first step and select your item in the batch modal.

I dont see the difference

I think the confusion is because the language string is wrong
it should not be Keep Original Tags
it should be Dont Copy or move

Yes, thanks for explainingt. The language string is the first reason for confusion. But it must be "select a tag". Just open the dropdown.

The second is: Why not accept the selection of items to move or copy from the overview? In com_menus and in categories we don't have an extra step for that. Maybe there is something special in tags which requires that?

@chmst Sorry I dont understand what you are talking about

I am sorry that I cannot explain. Will try it later with videos.

@brianteeman you were correct. - it seems that this language string caused the whole confusion and my folloing action was overreaction.
So it will be an easy fix. Thanks for your patience.

Sorry for that confusion. I fixed the text and updated the description part of the PR.

This pull request has been automatically rebased to 5.1-dev.

Please fix phpcs https://ci.joomla.org/joomla/joomla-cms/71117/1/7

I have tested this item ? unsuccessfully on 78aad67

My result for Test 2 looks like this, which is what i would expect. But its not mentioned in the test instructions.

Test 2
Tag4
-Tag2
--Tag3
-Tag1

Fails to copy the tags recursively, somehow the Tag 4 is added 2x, see Tag4 (15) and --Tag4 (8)?

Test 3
Tag4
-Tag2
--Tag3
--Tag4 (8)
---Tag2 (8)
----Tag3 (5)
----Tag4 (15)
---Tag1 (2)
-Tag1

I have tested this item ? unsuccessfully on 78aad67

When I try to do the first move of -Tag2 --Tag3 under Tab4, I do not even have a Move or Copy dialog/set of buttons underneath the "To Move or Copy your selection please select a Tag or parent item" dropdown.

:(

@exlemor You need to compile the Javascript using "npm ci" in order to test this PR

I have tested this item ✅ successfully on 78aad67

The process works, but in the batch a way to override the parent tag would be useful. Take it to the root level

@beni71 Thank you for your work, however it looks as if we need some more adjustments. It seems as if the hierarchy is not maintained? Could you have a look?

Hi all. Thanks for testing this feature. There are a couple of things I have to go one by one.

@steffans I'm not sure whether you didn't exactly follow the test instructions or you really found an issue. So let's go into details of test2 first:
The initial tag structure is:
Tag1
-Tag2
--Tag3
Tag4

Which means that Tag1 an Tag4 are both on root level, Tag2 is a sub-tag of Tag1 and Tag3 is a sub-tag of Tag2.
So when I move Tag1 to Tag4 then Tag1 should be a sub-tag of Tag4, like:
Tag4
-Tag1
--Tag2
---Tag3

Can you tell me how your repro steps were to get:
Tag4
-Tag2
--Tag3
-Tag1

@adj9 Regarding

The process works, but in the batch a way to override the parent tag would be useful. Take it to the root level

Do you mean something like: -Root-

Or what about: - No parent -

Extended the batch tag drop down with a "Root" item to move/copy selected tags to the root level, suggested by @adj9.
I updated the description.

@bembelimen Can you please tell me where the breaking change is? Do I need to fix it?

This pull request has been automatically rebased to 5.2-dev.

I have tested this item ? unsuccessfully on 715e848

The copy and move radio buttons did not show up for me.

did you run: npm run build:js first ?

Download Prebuilt packages result in a 404.

@Quy Thanks solving Problem.

I have tested this item ✅ successfully on 715e848

I have tested this item ? unsuccessfully on 715e848

The Copy/Move radio buttons do not appear. The action performed is Move.

I have tested this item ? unsuccessfully on 715e848The copy and move radio buttons did not show up for me.

This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/41927.

I just learned what an NPM patch is and that it can't be tested through the patchtester as I was using it on a copy of my live site on the server. So please disregard my failed test!

I have tested this item ? unsuccessfully on 715e848The Copy/Move radio buttons do not appear. The action performed is Move.

Bruce @bascherz, did you use the patch tester extension for your tests? Pull requests that are tagged 'NPM Resource Changed' need to be tested locally, they cannot be tested straight from our PBF instances, unfortunately. That's because a script file has been modified and the Joomla instance needs to be rebuilt to be able to get tested.

I just learned what an NPM patch is and that it can't be tested through the patchtester

@cybersalt you can use instead a prebuilt package. Download at the end of this pull request.

So please disregard my failed test!

if you don't test again you can set back the test result at the issue tracker by "Test this > Not tested".

I have not tested this item.

My Pizza Bugs and Fun test was first marked as a fail, but then I learned that I could not test this one with the patch tester - so I am resetting this to "not tested" so as to not confuse things.

This pull request has been automatically rebased to 5.3-dev.