Redmine

The instances without sudo mode enabled won't be able to use this feature, right?

Marius BALTEANU wrote:

The instances without sudo mode enabled won't be able to use this feature, right?

Yes, that is right. The patch extends sudo mode, so there is no change in behavior on Redmine instances without sudo mode enabled.

Go MAEDA wrote:

Committed the patch.

Even if the patch is already committed, I think it's too much to require the password for delete actions and to have this feature only for the instances with sudo mode enabled. I think making the delete action harder, it's good idea. What I saw in the last period in many web applications (starting from cloud platforms to Github, Gitlab) it's a custom confirmation modal that requires a manual input like "yes" from the user in order to continue the action.

Also, in some cases like issue page, the delete button it's easily mismatch with the delete button from comment and what we can do there is to hide the button under actions dropdown.

I'm reopening this to take more feedback from the users, I don't think that such a change should go so quickly in the next release.

It will be nice if an alternative implementation is introduced before the release of 4.2.0.

But I believe that a mechanism to guard contents against such accidents is indispensable and the sudo mode works well until another mechanism is implemented. I will happily replace this if another patch is suggested.

Before that, I think the sudo mode is a good workaround. Probably not many instances enable sudo mode, the instances influenced by this extended sudo mode are limited. So, most users Redmine can delete contents as usual even after their instance is upgraded.

I support Go Maeda in this.

This happens so frequently (even to those like me that use Redmine daily for decade, due to that funky journal delete button being on wrong place) that its better to have current implementation then wait for something else. Is it really important what I type ? yes or password ?

This should eventually support bulk operation (not sure if it does now). It is very important for spammy plugins like service desks.

Marius BALTEANU wrote:

We can use the implementation proposed in #33071 to have this ticket done.

Indeed. It is a nicer solution.

We had actually thought about doing something like this for issue deletion as well, but found it a bit too intrusive in the end.

Few things I just thought about:

- we could use an overlay for the confirmation dialog instead of leading to another page. This would simply replace the 'Are you sure' alert that exists in many cases with something more meaningful, without distracting too much.
- for issues or other 'less important' entities, give the user an option to turn off the confirmation requirement until the end of the day. This would relieve people doing 'cleanup' style tasks from having to confirm each and every action.
- entering 'yes' (in case of bulk delete) or the issue id should be sufficient (I would not want to use the password for this kind of confirmation).