nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why can't my user see some stories in sprint (he has browse permission, no security settings)

Ashley Jean

After updating to v7.12.0 on our JIRA-server instance, one user has reported that he cannot see a subset of issues in the active sprint board (tagged with a specific component). The user can see stories with the component that are not in the active sprint as well as all tickets without the component. We do not use any kinds of custom security measures on individual issues.
Anyone have any ideas on what could be happening, and how we could correct it?

Accepted answers

Tinker Fadoua

Hi Ashley,

Did you check the workflow for any validations? or Conditions?

unknown

First: identify the problem

You said one user reported the incident, does it affect more users or only that user? If there are more users, are the same issues affected or there others?

Jira 7.12 is a release that changes indexing for datacenter and also the administration or filters and boards, so it can be a bug caused by the upgrade.

Check first the things I said above, also double check the filter in the boards before and after a reindex of the instance.

If the filter is not the problem, check the quick filters that user can be using. If you can't identify what can be causing this incident, then open a ticket in atlassian support.

All comments

Tinker Fadoua

Hi Ashley,

Did you check the workflow for any validations? or Conditions?

unknown

First: identify the problem

You said one user reported the incident, does it affect more users or only that user? If there are more users, are the same issues affected or there others?

Jira 7.12 is a release that changes indexing for datacenter and also the administration or filters and boards, so it can be a bug caused by the upgrade.

Check first the things I said above, also double check the filter in the boards before and after a reindex of the instance.

If the filter is not the problem, check the quick filters that user can be using. If you can't identify what can be causing this incident, then open a ticket in atlassian support.

Ashley Jean

Thanks for the insight. We finally figured it out. Apparently there was a copy of the scrum board that the user somehow got on. Once the unnecessary copy was removed, all was well again.

Tinker Fadoua

Good to know! Thank you for taking time to share the fix @Ashley Jean!

Ashley Jean

Thanks! The problem turned out to be a filter, but not in the way you'd think. The user somehow flipped to a copy that someone made of the scrum board. We got rid of the unnecessary board, and that corrected things.

unknown

Awesome! I was scared that it could be a bug of the upgrade process, glad to hear it!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server