Compass component search breaks after exactly one minute

Tim Whittington December 3, 2024

We just started using Compass components and have noticed a very odd behaviour where searching for issues using a filter on a component breaks after one minute.

 

Steps to reproduce:

  • alter the component of any issue (e.g. a component or remove it)
  • query for issues, filtering by a component (does not have to be the one added/removed, but should return some issues)
    (e.g. project = "PRJ" and component = my-component)
  • repeat the query, observing that it succeeds each time
  • wait for exactly 1 minute after the original issue was modified
  • repeat the query, observing that it no longer returns any results

This breaks filtering by component for our entire instance (other users, other browser sessions) until the next time an issue is modified (changing any field appears to work).

 

Has anyone else encountered issues with Compass components?

2 answers

0 votes
Tim Whittington December 12, 2024

Interestingly this has now started working (after being consistently broken for a number of months), so if there's an anonymous support type out there that did something to resolve this, thank you...

 

0 votes
Doris Margraf December 11, 2024

I experienced a similar problem, but any filtering for Compass component did not work at all, except on my Kanban board. So backlog, or general filters never considered my components I have added on my issues.

For now I only had 1 resolution: go back to Jira Components and deactivate Compass. But there was some extra work in fixing tickets manually.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events