Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,559,187
Community Members
 
Community Events
184
Community Groups

Configuration Manager: unable to perform deployment due to filter

Luca Andreatta
Luca Andreatta
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
Apr 21, 2023

Hi, I'm tryng to import a snapshot in our Jira instance, but I get this error:

Unable to perform deployment: Unable to apply change 'type: addition, object: JiraConfigurationRoot@root/JiraFilter#Issue da Referente interno_ig01909, target object: JiraConfigurationRoot@root, feature: filters'

 

As I see there is some problem importing a Filter, but I don't understand why. Does anyone can help me?

Thanks in advance!

Answer
Watch
Like Oleskandr Kurtanych likes this
180 views

1 answer

0 votes
Dan Stroud
Dan Stroud Jun 04, 2023

I typically run into this problem when filters are owned by accounts that don't exist within the Jira instance.  Check the account ownership on the filter first.

Reply

Suggest an answer

Log in or Sign up to answer
Product apps
Apps & Integrations
TAGS
AUG Leaders

Atlassian Community Events

See all events