Possibility to change / add bulk actions within overviews

[Vogelkoje]

Infos:

• Used Zammad version: any
• Installation method (source, package, ..): any
• Operating system: any
• Database + version: any
• Elasticsearch version: any
• Browser + version: any
• Ticket: # 1077191, # 1078751, # 10103280, # 10139184, #10146791

Desired behavior:

• If several tickets are selected in the ticket overview, more attributes should be available than just group, owner, status and priority.

Actual behavior:

• Only the attributes group, owner, status and priority are currently available. None can be added.

Steps to reproduce the behavior:

• Go to a ticket overview
• Select multiple tickets
• Below you can see the possibility of a collection campaign

[MrGeneration]

This will need specification, as I personally don't think you'd technically want to have all available attribute for a ticket at that point.

As I know fairly big instances, the attribute listing would hide the overview content which I suppose is not the goal.

[Prodeguerriero]

Hey @MrGeneration,

[...] as I personally don't think you'd technically want to have all available attribute for a ticket at that point.

I think that every attribute that can be changed inside a ticket should potentially be changed when trying to bulk-update tickets. This saved my butt multiple times when I was still in customer support, managing Zendesk.

I also have a current example. I am thinking of replacing an object that was created as Select with a Tree select. Being able to filter the tickets based on the value of the former and bulk update the value of the latter would be very practical.

Here is how the Zendesk UI handles this:

1. Select multiple tickets
2. Click on a button called Edit tickets
3. Use the pop-up window to edit all the fields you need to edit

• Use macros (in Zendesk macros cover the functionality of both Zammad's text modules and macros)
• Choose a new status if needed

4. Submit the edit

Here is what the UI looks like:

[MrGeneration]

@Prodeguerriero thank you very much for your Feedback. Just to make my statement above clear (why it's so specific):

My comment currently expects no UI change (which would be required by your approach).

Don't get me wrong, I don't dislike or hate the idea - it's valuable feedback and may help to find a good approach. 🙌

[jannheider]

What about to let the Admin/User select which Objekts to have as Bulk Aktion We Still can keep 4 Bulk Objects as is or 5 if it fits in the GUI

[Matt-CyberGuy]

Where do we find this? We just installed zammad to test out and absolutely need this feature!

[Prodeguerriero]

Where do we find this? We just installed zammad to test out and absolutely need this feature!

Hi Matt,

You are adding a comment to an open feature request, which should already answer your question. May I suggest asking for a timeline instead?

[Matt-CyberGuy]

Ahh, my mistake, I followed a link from google and got excited thinking this was a feature we somehow didn't have turned on. Is there a timeline for this?

[MrGeneration]

We in general do not provide any ETA sorry. If you can't wait for a specific feature, there's always the option to boost it by sponsoring it's development.

Drop us a line to sales [at] zammad [dot] com in case you're interested.

---

In general issues will tell you which states they have. Project and Milestone are a indicator if something starts moving.

[trent823]

Also interested in this feature