Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,639,450
Community Members
 
Community Events
196
Community Groups

Filter has stopped working since update

Edited

Our IT installed some of the recent updates, and since then a filter we have had set up that has worked fine for over a year, has stopped working.

The filter was originally set to this: 

project = BIT AND labels in (Monthly, QM1) AND "Epic Link" = BIT-2068 ORDER BY summary ASC, priority DESC, updated DESC

Now it only works if we remove: AND "Epic Link" = BIT-2068

which doesn't help us at all as we need to limit the filter to tasks that are in that particular epic.  

Has anyone else had any issues with filters since updating their JIRA? Can anyone think of a work around?

Many thanks.

 

ETA:  I've checked and I can filter other Epics, just not this one.  Not sure if that helps anyone think of an answer?

1 answer

1 accepted

0 votes
Answer accepted

As other Epics were able to be filtered I have resolved this by creating a new epic, assigning all of the tasks to it, deleting the old epic, and then amending the filters to point to the new epic.  Quite a bit of work but at least it's working!

Suggest an answer

Log in or Sign up to answer