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 to create a dashboard for a specific set of issues?

Josh Goldberg

I'd like to create a dashboard (or page) that includes issues (bugs) of my choosing; not per any specific filtering criteria. My specific usage is to keep track of all issues that I need (or would like) to respond to. These issues are not necessarily assigned to me, and I don't want to introduce a new attribute for only this purpose.

Ideally, I would drag/drop issues to and from this new dashboard. I do not want to have to set up a filter that explicitly names each issue (but realize that this is possible).

How can I do this?

Accepted answers

Nic Brough -Adaptavist-

How is Jira supposed to know what you are interested in if you don't tell it?

You need to have a rule that it can follow to answer the question "what is Josh interested in?", which means putting something on an issue to tell it. Sometimes, that could be a rule based on existing data like "bugs in project X, Y or Z that have not been updated for 3 days", but sometimes it won't be, and you'll have to come up with something that involves adding the "Josh is interested" flag.

As soon as you do that, you have something you can filter on, which means you can create dashboards based on that filter.

There are two obvious candidates for "I'm interested" which work very well.

Making yourself a watcher - it's a simple "watch this" click on an issue, and you can easily un-watch when you lose interest (en-masse if you want).
Adding a label like "josh_should_see_this" - a little more effort and easier to abuse as a label field can be changed by anyone who can edit

Both of these are really simple to filter for and hence use on a dashboard.

There is nothing in Jira resembling "drag and drop on to a dashboard" though. You'll have to identify and update your issues via edits/watches.

All comments

Nic Brough -Adaptavist-

How is Jira supposed to know what you are interested in if you don't tell it?

As soon as you do that, you have something you can filter on, which means you can create dashboards based on that filter.

There are two obvious candidates for "I'm interested" which work very well.

Making yourself a watcher - it's a simple "watch this" click on an issue, and you can easily un-watch when you lose interest (en-masse if you want).
Adding a label like "josh_should_see_this" - a little more effort and easier to abuse as a label field can be changed by anyone who can edit

Both of these are really simple to filter for and hence use on a dashboard.

There is nothing in Jira resembling "drag and drop on to a dashboard" though. You'll have to identify and update your issues via edits/watches.

Josh Goldberg

Hi @Nic Brough -Adaptavist-, thanks for your quick reply.

How is Jira supposed to know what you are interested in if you don't tell it?

To be clear (which perhaps I was not) it's not simply a matter of what I'm interested in. I need to create a kind of to-do list for items that I need or would like to respond to, even though I'm not their owner.

Existing mechanisms are not favored for the reasons given:

Watcher: I am a watcher on many more items than I need to respond to.
Label: you explained the problem

Indeed, that was the idea of drag and drop, as a very easy way of adding/removing an item to/from my "to-do list".

What I can do now is build and save a query of this form:

key IN (issue1, issue2, ...)

Of course, this involves manual editing to add/remove the issues. That's not too bad when there are a small number, so I suppose I can live with it.

Nic Brough -Adaptavist-

Whatever you do, you absolutely need to have some way of telling Jira you are interested in an issue for some reason. There is no way around that, you need to flag them so they will appear in a search somehow. There's no way it can just guess what you want, so yes, you may have to simply hard-code a search.