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

Jira Kanban with Swimlanes and Query problem: Issue does not exist or you do not have permission to

Mark Corrigan_1efc9r

Hi Can youall assist me.

I have a Kanban board with a swimlane which has a number of Epics that are selected via the query area.

I.e.

parent = DIPB-391 OR parent = DIPB-429 OR parent = DIPB-436 OR parent = DIPB-437 OR parent = DIPB-438 OR parent = DIPB-445 OR parent = DIPB-447 OR parent = DIPB-453 OR parent = DIPB-464 OR parent = DIPB-469 OR parent = DIPB-484 OR parent = DIPB-118 OR parent = DIPB-496 OR parent = DIPB-499 OR parent = DIPB-500 OR parent = DIPB-504 OR parent = DIPB-510 OR parent = DIPB-565 OR parent = DIPB-567 OR parent = DIPB-568 OR parent = DIPB-171

WHEN I TRY TO ADD ANOTHER EPIC I GET THIS ERROR FROM JIRA:

"Issue does not exist or you do not have permission to see it. Update the query and save it again."

I try to fix this I have done:

a) deleted cookies in the browser.

b) deleted the Epic and tried to add another epic with a new number. i.e. OR parent = DIPB-234

c) scoured the internet and Jira and Atlassian forums

All to no avail.

I need to be able to add in a number of other Epics and am now blocked from doing so.

Please can you assist me.

Accepted answers

Bill Sheboy

Hi @Mark Corrigan -- Welcome to the Atlassian Community!

Have you confirmed that the additional issue key you added exists and you have permission to access it?

Have you confirmed that for the issues which are child issues of the newly added key, you have permission to access them?

If so, I have never encountered a maximum size limit for the swim lane queries...but that does not mean there is none. Perhaps try changing your query to use the IN operator rather than the OR keyword. For example:

parent IN ( DIPB-391, DIPB-429, DIPB-436, DIPB-437, DIPB-438, DIPB-445, DIPB-447, DIPB-453, DIPB-464, DIPB-469, DIPB-484, DIPB-118, DIPB-496, DIPB-499, DIPB-500, DIPB-504, DIPB-510, DIPB-565, DIPB-567, DIPB-568, DIPB-171 )

Kind regards,
Bill

All comments

Karan Sachdev

Hey @Mark Corrigan

Welcome to Atlassian Community!

Could you elaborate on your use case/requirement? Swimlanes are used to distinguish issues (work items) based on components, assignee etc.

Just want to get more details on why you're adding all Parent issues in a single swimlane query. Do you want to display the child issues of all these Epics on your board?

Thanks!

Mark Corrigan_1efc9r

Hi @Karan Sachdev The parent items are Epics. I.e. we have a swim lane that is busy with a number of Epics while another only focuses on a few.

The Kanban board divides up the work for the department into swim lanes.

The key point of the joint board is to offer an overview to all the teams and managers of the work being done. Queries are also used to target users who are allocated to do work across a number of swim lanes (business areas).

Note: We are well aware that different boards can be used but management wanted a simple overview which included swim lanes.

Our concept is working well. However, for some reason, I am unable to add any more items into the list of Epics. I read something about a limit of 255 but this does not apply. I.e. my list above is 430 odd characters.

Any help on this will be appreciated.

Mark Corrigan_1efc9r

@Karan Sachdev I have tried another solution. Thinking that I may have reached some limit in the query section of the swimlane I tried to delete (remove) one of the items in the query list above. i.e. OR parent = DIPB-436 . I again received the error above in red text: I.e. * Issue does not exist or you do not have permission to see it. Update the query and save it again. Bottom line: for some reason I (administrator and creator of the board) am unable to add to or delete the query list.

Bill Sheboy

Hi @Mark Corrigan -- Welcome to the Atlassian Community!

Have you confirmed that the additional issue key you added exists and you have permission to access it?

Have you confirmed that for the issues which are child issues of the newly added key, you have permission to access them?

Kind regards,
Bill

Mark Corrigan_1efc9r

Thank you! The change in JQL has helped. I believe an Epic may have been deleted. When I put the new coding format in Jira notified me that Epic number xxx was not available. I deleted that key and could proceed.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud