Batch modify should block tickets when selecting unavailable action for the tickets

[Jun Omae]

When [ticket-workflow] has the following actions and both reopened and closed tickets are shown in custom query, both resolve and reopen actions are available in batch modify form.

resolve = new,assigned,accepted,reopened -> closed
resolve.permissions = TICKET_MODIFY
resolve.operations = set_resolution
reopen = closed -> reopened
reopen.permissions = TICKET_CREATE
reopen.operations = del_resolution

Then, if a user checks reopened and closed tickets and submits with resolve action, the resolve action wouldn't be applied to the closed tickets. The behavior is right but just confuse the users.

I think we should block submitting batch modify form when selecting unavailable actions for the tickets.

Example: it seems that resolve action is available for #2 in query:id=2|12449 but #2 has been resolved.

[Ryan J Ollos]

Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.

[Jun Omae]

A user pointed out this issue on production environment. At least, I want to show warnings after submitting batch-modify form.

[Ryan J Ollos]

Milestone renamed