nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

BULK Delete

Alison Whittle

The new bulk delete feature on the filter page is very dangerous!

It doesn't ask to confirm deletion or run through the bulk update process anymore. It's also a menu item next to the 'close' cross icon which is a dangerous too and could easily be pressed by mistake.

Appealing to the product team, this UX is not a good for such a dangerous bulk action. It needs to have a process flow to ensure the user can't do anything by a rouge mouse click!

Accepted answers

Arkadiusz Wroblewski

Hi @Alison Whittle

I'll request Atlassian assistance to have this investigated.

Best,

Arek🤠🧙‍♂️

Artyom Karpets _ArtUp Labs_

Hi Alison, agreed that a one-click delete for a whole selection is risky. Until the UX changes, you can limit who can reach it:

Deleting several work items at once needs the global permission Make bulk changes (Atlassian's "Manage global permissions" page: users with it can "edit, move, or delete multiple work items at the same time", provided they have the space permissions). Check which groups hold it in Jira settings → System → Global permissions.
In each space's permission scheme, give Delete work items only to admins or a small role.

With both in place, a stray click by most users does nothing, while bulk edit and bulk transition stay available to whoever keeps Make bulk changes.

For the UX itself, a suggestion on jira.atlassian.com (JRACLOUD) that you link here lets others vote on it.

Written with help from an AI assistant.

All comments

Arkadiusz Wroblewski

Hi @Alison Whittle

I'll request Atlassian assistance to have this investigated.

Best,

Arek🤠🧙‍♂️

Artyom Karpets _ArtUp Labs_

Hi Alison, agreed that a one-click delete for a whole selection is risky. Until the UX changes, you can limit who can reach it:

Deleting several work items at once needs the global permission Make bulk changes (Atlassian's "Manage global permissions" page: users with it can "edit, move, or delete multiple work items at the same time", provided they have the space permissions). Check which groups hold it in Jira settings → System → Global permissions.
In each space's permission scheme, give Delete work items only to admins or a small role.

With both in place, a stray click by most users does nothing, while bulk edit and bulk transition stay available to whoever keeps Make bulk changes.

For the UX itself, a suggestion on jira.atlassian.com (JRACLOUD) that you link here lets others vote on it.

Written with help from an AI assistant.

Rick Westbrock

It is odd that when deleting a single work item we get a confirmation dialog box but not when doing a bulk deletion; I would have expected that to be the other way around.

Arkadiusz Wroblewski

Hm, consistency are not always there

Samuil Enchev

Hi @Alison Whittle,

Thank you for reporting this.

I shared this with our design team, but after their initial testing, they were unable to reproduce the issue. They tested both the filters and the issue navigator pages, and the confirmation modal appeared as expected in every instance.

To help us investigate further, could you please clarify which specific page or experience you are using when this occurs?

Best,
Samuil

Alison Whittle

Hi Samull

This is on the filter page, we ran our JQL to select records, clicked the Select ALL (Bulk select) and then the screenshot in my initial post shows the menu item that appeared. Instead of clicking on the 'X' close (as we were just checking at this stage) we accidently clicked on the delete and the system deleted everything within the query. We lost around 300 issues, so like I say, its dangerous that the system did not even check we wanted to go ahead with the delete, let alone going through any belts and braces bulk update process!

Sorry your unable to replicate, but we are still feeling the pain of it happening!

Samuil Enchev

Hi @Alison Whittle,

I understand this issue must be frustrating for you. I've created a support ticket on your behalf - PCS-3876602.

Because you have two Premium Jira instances, I had to select one to create the request. Please jump into the ticket and confirm which instance is affected so our engineers have the correct details to start their work.

As a Premium customer, you can also reach out to us directly via Atlassian Support for any future issues. This is the fastest way to get dedicated support from the right team.

Best regards,
Samuil

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

bulk-delete