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 mobile app is not showing tickets by selecting Base Swimlanes on Story while desktop app shows?

Deimantas Norkeliunas

Here is the screen of configuration:

Screen Shot 2020-12-21 at 22.44.28.png

Desktop app shows all tickets:

Screen Shot 2020-12-21 at 23.00.36.png

While mobile app just a few of them (should show 18 issues):

Where is the problem?

If I change swimlane by Queries, it shows everything correctly. The problem exists only with Stories selection.

JQL query: project = LETS ORDER BY issuetype ASC, priority DESC

Accepted answers

All comments

Angélica Luz

Hello @Deimantas Norkeliunas,

Thank you for reaching out to Atlassian Community!

Testing on my local site, I created a board and added JQL and also the swimlanes based on Stories, but I wasn't able to replicate the issue.

On both Android and iOS it shows the swimlanes:

Screen Shot 2020-12-22 at 15.39.20.png

Can you please let us know what is the app version you are using?

Also, I see that the stories are on the status Closed or Backlog, is it happening when the status of the story is To Do?

Regards,
Angélica

Deimantas Norkeliunas

Damn. I want to have the same view 😏

I’m using beta testing build.. maybe I should delete and install production version?

--
Regarding statuses:

Screen Shot 2020-12-22 at 20.52.18.png

Angélica Luz

Thank you for the screenshots, @Deimantas Norkeliunas

I tested here and removing the status Backlog from the board, will remove the issues from the board when viewing it on the mobile.

You will need to map the Closed status, in this case, add it to the Done column and also change the status of other tickets from Backlog to one of the statuses visible on the board.

After that, the swimlanes should be visible when using the mobile app.

Please, give it a try and let us know how it goes.

Deimantas Norkeliunas

@Angélica Luz hello 👋

Thanks for taking care of it.

Why do I need to map Closed status with Done? I don't want to display issues in the Kanban board which are Closed.

* For me Closed stands for Archived and I don't want to show or see those issues in the Kanban board.

Some subtasks (passive or not MVP) are the subtasks of actual issue which is visible in the board along with other active subtasks.

I don't want to show passive subtasks in the Kanban board so I can keep my team attention on MVP issues.

**Passive subtasks are created just not to forget to deliver them with other iterations so they can wait in the backlog.

If I follow your recommendations I will mess up with my Desktop Kanban board view which is correct.

In this case Mobile Kanban board view is not correct and it suppose to follow the Desktop Kanban board view.

Do you think it's a bug on the Mobile app that it doesn't shows all issues which you can clearly see on the Desktop app?

Thank you 🙏

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

app

mobile