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; } } }

Tickets going Missing

Roja Gurram_ey6522

All,

1) USER uses the two boards. When USER (A) takes a ticket from the ONE board it is automatically putting it into her own board and removes it from Rekha’s (B) ( Other user who is the owner of the board 'Rekha' for understanding i elaborated ) visibility and her stats.

2) There is also issues when USER then closes the tickets that the AR collectors cannot view.

Can someone advice why this is happening pls?

Accepted answers

Nic Brough -Adaptavist-

We don't know who Danielle is, or what she has explained, nor do we know who Rekha is.

However, yes, we can tell you what is happening.

1) Boards are not containers for issues, they are a view of a selection. Issues do not move from one board to another.

What is happening here is that the ONE board is selecting one set of issues and the other boards have different selections and you are changing data on the issue that stops the ONE board and Rekha's board selecting it, while also making it selected on the user's board.

My best guess is that the boards are selecting by assignee, and so reassigning the issue makes it de-selected be some boards and selected by others

2) Your AR collectors do not have the right permissions to see the issues. Check the project's permission scheme and issue security scheme to see why

All comments

Nic Brough -Adaptavist-

We don't know who Danielle is, or what she has explained, nor do we know who Rekha is.

However, yes, we can tell you what is happening.

1) Boards are not containers for issues, they are a view of a selection. Issues do not move from one board to another.

My best guess is that the boards are selecting by assignee, and so reassigning the issue makes it de-selected be some boards and selected by others

2) Your AR collectors do not have the right permissions to see the issues. Check the project's permission scheme and issue security scheme to see why

Roja Gurram_ey6522

Hi Nic,

Thanks a lot for your response.

1) Thanks for clarification.

2) Your AR collectors do not have the right permissions to see the issues. Check the project's permission scheme and issue security scheme to see why-

Ok, Do you want me to check whether the AR Collectors have access to the project? There is no VIEW ISSUE specific permission in Jira server 7.3.1 Version. Also Just to confirm "Issue security Scheme" is not set to this project.

Any suggestion would be appreciated!

Nic Brough -Adaptavist-

Yes, that is what I said. It's "browse project" permission they need (it's not the best phrase atlassian could have chosen there, it really should be something like "view project issues")

Roja Gurram_ey6522

Thanks for your help Nic.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server