Re: [Tiki-devel] Discussion about tracker item duplicate feature in case the tracker use a field user selector with auto-adssign

> Tricky one, maybe it should ask?

Yes that’s why we are on the devlist. ;-)


Time for the long detailed explanation…

I see a 2 use cases for duplication (People see more ? please add to the discussion)

- admin duplicate from the tracker view (using the command using Smarty template is the same)
- user duplicate from tracker view (using the command using Smarty template is the same)

(Things done using the plugin list Execute are different and the action name is “Clone” and not “Duplicate”. (Detailed below for better comprehension)



-= Based on Tiki25 tests =-

From the tracker view, the actual behavior:
When you duplicate an item in Tiki you don’t have a real duplication; categories reseted to blank, selected user with auto-assign set to creator is changed, status is changed to the tracker new item behavior, etc…

Meaning of duplicate in English (https://dictionary.cambridge.org/us/dictionary/english/duplicate)
duplicate, verb [ T ], us, /ˈduː.plə.keɪt/ uk, /ˈdʒuː.plɪ.keɪt/
to make an exact copy of something: something that is an exact copy of something else:


It is disturbing to do a duplication and to end with something else without any explanations. (Tiki don’t do what it says... for new comers)
Especially that we don’t have good doc a simple explanation to give. (One sentence onscreen explanation)
So we need to understand that in fact, Tiki is not duplicating but rather create a new item based on a previous one. 🫢

Based on this, to improve the situation for the user selector with auto-assign set to creator issue we could add:

- A per tracker switch, it will add more confusions (set in a place without any context related to the field - not very user-friendly or intuitive)

- A general switch under the tracker duplicate feature switch (control panel Trackers): “If a User Selector with auto-assign and is set to creator exist, the new item will reset the field to the new item creator (default). Keep untouched the User Selector fields with the previous user selected.”  This is a minimum done.

- A per user Selector switch will be good (better control and easier to understand as related to the context = no doc needed) - a child option of auto-assign selection “Creator” :
“When using the duplicate feature, apply the setting and reset the creator of the item to the user doing the duplication (default) or keep the previous selected user through the duplication.


> For a non-admin i guess the "creator" user selector should be set to the user doing the duplicating,


As set by the switch above ? (A per field option make this choice much easier too)


More seems to me overdoing as usage of this excellent feature seems to be low, and we want to avoid too much coding,
Ideally, we could have a modal with notices or questions (category are not part of the duplication, do you want to keep categories, do you want to keep user, etc)

—





For wider view we have this is not to be mixed with the list execute, where we don’t have a duplicate action but a “clone” action.
Using action clone, categories are reseted to blank, dates (if set to today) are reseted but the selected user and status are kept as is.

For me (my usage) it is a much better/clearer situation.
You duplicate and you have almost a perfect duplication.
Category or date can be set using “tracker_item_modify” or “tracker_item_insert” actions.

I have no problem having the described above "user selector switch" applied here or not. (It will add flexibility)

Bernard



> On 24 Feb 2023, at 18:44, Jonny Bradley via TikiWiki-devel <[email protected]> wrote:
> 
> Hi Bernard
> 
> Thanks for kicking this off - i'm far from clear what the behaviour should be, especially for an admin.
> 
> For a non-admin i guess the "creator" user selector should be set to the user doing the duplicating, but for an admin i'm not so sure. Should it duplicate the current creator user, or use the current user (which is what it does now) or... something else?
> 
> Tricky one, maybe it should ask?
> 
> jonny
> 
> 
> 
> 
>> On 23 Feb 2023, at 14:01, Bernard Sfez <[email protected]> wrote:
>> 
>> Hello all,
>> 
>> With Jonny and Victor we discussed about a bug/problem related to the duplicate tracker item feature when the tracker field as a user selector with an auto-assign option.
>> 
>> In such case, cloning creates an item and the user cloning the item is auto-assigned which might be desired or might not.
>> IE: if admin duplicate an item he will be technically the item creator of the new item and therefor the username from the parent item will be changed for admin.
>> 
>> We discussed about adding a switch to keep this behavior and to cancel it (user selector is preserved when duplicating the item).
>> 
>> We would like to check with others what would be the best solution;
>> 
>> - A per tracker switch
>> - A duplicate feature switch (all trackers)
>> 
>> For all the use cases I can think of, a “cheaper” general setting (all tracker affected) will be good.
>> 
>> Do people think of cases it will be needed to modify the creator of an item ?
>> What people think ?
>> 
>> Bernard
>> 
> 
> 
> 
> _______________________________________________
> TikiWiki-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel

_______________________________________________
TikiWiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel