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; } } }

Is there a way to do a bulk change for all filters using a project name that has changed?

Steve Hooczko_zrtbba

The name of a project has changed (Key is still the same) and I need to change all filters that use "project =" or "project IN" and replace the old name with the new one.

Is there a way to do this without changing the filters one-by-one?

Accepted answers

Linh Pham_Kolekti _Adaptavist_

Hi @Steve Hooczko unfortunately there's no way to bulk update filter in your case, and Atlassian has no plan to implement this featurte request https://jira.atlassian.com/browse/JRACLOUD-39724

All comments

Linh Pham_Kolekti _Adaptavist_

Hi @Steve Hooczko unfortunately there's no way to bulk update filter in your case, and Atlassian has no plan to implement this featurte request https://jira.atlassian.com/browse/JRACLOUD-39724

Marc -Devoteam-

Hi @Steve Hooczko

@Linh Pham_Kolekti _Adaptavist_ is right on this.

Even on the marketplace there are no 3rd part apps for this requirement..

Andy H

As others have stated, there is no way for a Jira Cloud Admin to make this change to filters in bulk. If you only have a few dozen of filters to change, the quickest way to do this would be 1 by 1. That said, if you happen to have hundreds of filters to change, the scale of work before you is such that it's worth creating a support ticket with Atlassian support https://support.atlassian.com/contact

In some cases, support can leverage SQL to make changes on the database that your Jira Cloud uses. Granted this is not typically offered outright, and there is always risk associated with such changes being made to the Jira database. So it might depend upon a risk vs reward calculation to determine if support might be able to ease the pain of such a change. Personally I would doubt support would make this change for most cases, but I still think it's worth creating a support ticket to help Atlassian understand the customer pain around changes like this.

Steve Hooczko_zrtbba

Thanks Andy

Steve Hooczko_zrtbba

Thanks Marc

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud