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

Identify # of Issues in an Individual Project

andy.pawl

So my Atlassian friends - is there any way to do this?

I am running a BackUp/Restore to a stage instance and I am missing 193 issues - identified by using the Site Statistics plugin.

How do I isolate those issues to figure out the problem?

TIA

Accepted answers

andy.pawl

The solution is to create a filter of the Project and then on a Dashboard add the "Filter Results" Gadget - add the filter to that and save.

All comments

Piyush A (STR)

Hi,
Could be due to below:

Does the jql shows count in the source similar to stage instance? How did you counted the missing ones?
Try to compare the original issues keys in CSV vs stage instance issue keys (export the keys in CSV and. Do vlookup)
how was the backup/restore done?
does the projects have issue security in place? If so, then update your account with correct role or group based in issue security.

andy.pawl

The solution is to create a filter of the Project and then on a Dashboard add the "Filter Results" Gadget - add the filter to that and save.

Piyush A (STR)

Probably the question was about to identify the missing issues in the restore?

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