JIRA issues w/components defined - should filters / searches return results based on component?

I have a project with several components defined and assigned to issues. When I navigate to project overview > components > click a component > click issues for that component - there are no results. I can confirm that there are issues with this component assigned to them. What could be going wrong?


I also cannot create a filter with this project and the component name to return any results. If I just search for the project, then I get all my project issues. If I add the component column to the results, I then can see the components of the result issues there - but again I cannot search strictly via components and have the issues with those components turn up in the results.



1 answer

1 votes

Ok, start by picking out a couple of issues that 

First, are your issues resolved?  I.e. are they showing something other than "Unresolved" (note that I really mean it about the italics - that's an important part of the question) when you look at them on the issue view?

Second, is the component field definitely filled correctly when you check the issue view?

Third, can you search for these issues (via project or assignee or something) and include the components column in the navigator?  Do you get components displayed there?

Hi Nic, Thanks for your response. 1. Majority of issues are "Unresolved" (with italics). 2. Component field is definitely filled out when I view issues. 3. Yes, I mentioned this in my initial question. When I search for all issues via project = xx and add component column, it shows the component value. It's a strange result. I would expect to be able to search via component from issues search as well as through the project overview > component screens. Any thoughts?

I just wanted to be 100% on those points. Next step - could you try re-indexing the project that one (or more) of these issues is in? Then try searching again.

Oops, and could you also check your list of custom fields for a field called "component" or "component/s"?

Yup. There is a custom field called component for this project... Does that mean that the components defined for this field are not registering as native components?

Ahh, I see. Well, it sounds like you've ended up with two component fields. So I suspect your searches and issue navigator are failing because you're searching for one of them using the other field. A really easy test (and possible fix) for this - rename the custom field from "component" to "our internal components" or something else just as obvious and very different from "component". This won't affect your data in any way, but will make it completely clear what you are searching for and what appears in the navigator.

That was it. They have the same native jira components defined as their custom field "component" which has the same values defined. Thanks Nic!

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,887 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot