Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

wrong component in Jira scrum board

Mohamed Umar Fayaz M September 21, 2021

Hi,

 

We have created the scrum boards based on components in our project. A few days back ,  it is been observed that scrum boards are pulling a wrong component tickets which is not defined in the filters.

The tickets created from the certain date are only appearing in the wrong scrum boards and the same component tickets that are created earlier are not reflecting. we have not done any new changes in the filter. But, it is started showing all of us sudden since few days back onwards

  1.  Checked the tickets and confirmed that components are correctly defined with in the tickets as per the filter query defined for scrum boards.
  2. Resaved the filter and checked the scrum board,  but the result is same(wrong component tickets are still reflecting into the scrum board)
  3. Created a new ticket with the same component and other details of problematic ticket . But the result is same.
  4. The issue with specific component which follows the format of AB  XYZ(XX) and the other components which follows the same format are not getting pulled into wrong scrum boards .
  5. Checked if the "other components" (in the same scrum board where the problematic component is actually associated) reflects into other scrum boards or not. And, observed that those are not reflecting.
  6. Tried with adding condition of scrum team label ( for e.g : query like AND Labels in (“Team_ABC”))  to prevent from filtering the other scrum board tickets, tried with inside and out set of conditions. But the result is same in all trials. Looks like this works for scrum board works  well which is defined based on labels. 
  7. Tried with the condition label Not in(“label of scrum team where the problematic component associated”) to prevent the tickets from other scrum board. But, the particular component tickets are alone pulled.
  8. Tried with the condition AND component NOT IN ("problematic_component_name") in the filter to prevent this component in irrelevant scrum boards. But, still the same problematic component tickets are pulled.

 Does Atlassian faced similar issue with other customers and let me know if you have any work around or solution for the same?

Thanks in advance.

3 answers

0 votes
Nic Brough -Adaptavist-
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.
September 22, 2021

Boards will only show you issues that you choose to select.

You've described a lot of things you've tried, and bits of the config, but not the one thing that really matters.

Could you show us the board filter for a board that you think is showing the wrong issues, and the issue view of an issue you think should not be on the board?

0 votes
KAGITHALA BABU ANVESH
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.
September 22, 2021

Hello @Mohamed Umar Fayaz M

 

I think you belongs to Jira cloud. due to this Re-index will not possible, as the option is missing in jira cloud.

as you saying some date related concern. can you please check the jira board filter query. any date is added for issues retrieval of issues ?

 

Thanks,

Kagithala Babu Anvesh

Mohamed Umar Fayaz M September 22, 2021

HI Kagithala,

 

We dont have any date set in filter query. some component comes suddenly which is not as per the JQL in filter.

 

-Fayaz

KAGITHALA BABU ANVESH
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.
September 22, 2021

Based on the board JQL, issues will be displayed on the board Scrum / Kanban.

If you saw some unwanted issues on your board means --> it's time to modify the JQL of the BOARD, as per your customization.

if you don't have edit permissions, please contact filter owner. 

if the person left you can change the owner of the JQL by 

settings --> system --> shared items --> filters --> change owner (this can be performed by jira admins)

 

Thanks,

Kagithala Babu Anvesh

0 votes
Suvarna Gaikwad
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.
September 21, 2021

@Mohamed Umar Fayaz M can you try to do indexing for the affected project and see if it helps.

Suggest an answer

Log in or Sign up to answer