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

How do i view my tasks across multiple boards?

Zachary Whitely_ie05t4

I'm a UX designer that works across multiple JIRA projects: our design system, our infrastructure team, and multiple products.

Is there a way of creating a master board in JIRA that lets you see all of your tasks/issues/stories in the one place? I'm currently using ToDoIst to create copies of all of my JIRA tasks across projects and prioritising there.

Accepted answers

Lydia M

Hi Zachary! I'm with Martin, it seems like the best way to view all your issues across all projects would be to create a filter for all the issues you created/reported, etc.

If you need to see all those issues on a Kanban board, you'd have to create a project (for yourself) where you use that filter to populate a board.

We do something similar to this for subtasks that go to a specific group of people within the company (i.e., QA, Functional Testing). It's just the filter that populates the board, so the principle should be the same.

Hope this helps (and I'm not completely wrong, lol)!

All comments

Martin Bayer _MoroSystems_ s_r_o__

Hi @Zachary Whitely welcome on the community.

I will try to help, but let me ask you a question. What do you mean by board? Do you need to display all the tasks as Scrum or Kanban board? Or filtered issues with sorting is enought?

Zachary Whitely_ie05t4

Hi Martin,

Ideally I'd be able to create my own Kanban board to be able to prioritise my tasks using a few basic ToDo/Doing/Done swimlanes. But it'd probably suffice to be able to see all of my tasks/issues/stories (maybe grouped by priority or status).

It's a bit tricky as I'm basically a UX 'team' even though I'm a single person.

Lydia M

Hi Zachary! I'm with Martin, it seems like the best way to view all your issues across all projects would be to create a filter for all the issues you created/reported, etc.

If you need to see all those issues on a Kanban board, you'd have to create a project (for yourself) where you use that filter to populate a board.

Hope this helps (and I'm not completely wrong, lol)!

Zachary Whitely_ie05t4

Hey Lydia (and Martin), Thanks for your help.

I've made a filter that's filtering to anything I've created or assigned to me: assignee = ZWhitely OR reporter = ZWhitely AND status not in (Done)

However, I still see my Done items in the list. Any ideas how to remove items that have been marked Done? Is it to do with the board configuration or the way I've constructed the filter?

Bill Sheboy

Hi @Zachary Whitely

Looks like a query order parsing issue... Jira is OR'ing everything after the reporter check because the assign and reporter check are not grouped with parenthesis.

Please try this to see if it returns what you want:

(assignee = ZWhitely OR reporter = ZWhitely) AND status not in (Done)

Best regards,

Bill

Zachary Whitely_ie05t4

Hey that worked! Thanks Bill

Nir_2djt1v

Hi, I'm joining the question.

Our company provides development services for multiple customers.

I'd like to:

(1) Be able to get the whole picture about the team from one board

(2) Allow customers get the picture of their project only

(3) Create users for the customers for what I described in (2)

The customers should be able to see only their tasks and not others.

I've been using Jira for almost 10 years by now and I have no idea how to do it.

Will appreciate your help with that.

Thanks,

Nir

Lydia M

@nir For this type of scenario, the best choice, I believe, is to create Groups, and assign users to the Group, then set up a permission scheme for your project so that these groups can only see the content you choose.

For example, let's say my default permission scheme lets the group jira-users access everything in my Jira instance. Everyone in the company is a member of jira-users.

I want to limit what a certain group of users can see, so I create a group called AlphaDes, and assign certain people to that group, but not the jira-users group.

I set up a project Alpha Design and in my permission scheme, I have two groups, jira-users and AlphaDes. The members of AlphaDes should only be able to see the project Alpha Design.

This is a very basic explanation, so if anyone has details to add, please do! I hope this was helpful.

Cheers,

Lydia

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-software

jira-software-server