Best way to monitor multiple JIRA issues

withonlyamap

Looking for advice on the best way to monitor the status of multiple JIRA issues. Ideally, I'd like to be able to have a list of issues together on a page where I can see the status; this page could be in Confluence or JIRA, really. Just somewhere where I can scan over the issues and see the status. 

The thing is, I'm not a developer, nor do I have any part in working through the tickets, but it would be nice to have a way to monitor them.

For additional context, I have a list of about 80 issuekeys from 3 different projects. I'm guessing this may be too large of a query for a filter. 

Any thoughts on this?

Rachel Wright

Hey @withonlyamap,

Do you have a way to identify the issues you care about besides the issue key?  I ask because a JQL query like:

labels = johns-cool-thing

is much nicer to write than a query like this:

key in (ISSUE-1, ISSUE-2, ISSUE-3...all the way to...ISSUE-80).

For the fastest loading, I'd recommend creating a filter in Jira and displaying those issues on a Jira dashboard.  You can also use the same filter on a Confluence page, but the dashboard will load faster.

Here's some documentation on creating the filter:  https://confluence.atlassian.com/jiracorecloud/saving-your-search-as-a-filter-765593721.html

Most Jira instances are configured to allow 1,000 issues to display at a time.  So don't worry about 80. 

Hope this helps.  If it doesn't just ask again and I or someone else will try again!

Rachel Wright
Author, Jira Strategy Admin Workbook