Projects Manager and Project Activity

Manage every project from one table, and find out which ones are still alive.

Projects Manager

What it does. Shows every project in one table: name, key, style, lead, issue count, last update and issue type scheme. Names, keys and leads can be edited inline, and projects can be archived or restored in bulk.

Use it when you need to see all projects side by side, or change the same thing on many of them. Jira makes you open each project separately.

Admin Toolkit → Projects ManagerIllustration

Projects Manager

Load Projects

View and manage all projects with inline editing for names, keys and leads.

	Name	Key	Style	Lead	Issues	Last Updated	Issue Type Scheme
	Operations	`OPS`	Company Managed	MRMarina Rocha	12,481	Just now	OPS: Scrum Issue Type Scheme
	Legacy CRM	`CRM`	Team Managed	JLJoão Lima	318	Never updated	Default Issue Type Scheme

Bulk actions — 2 projects selected

Change LeadTransfer LeadArchiveRestoreConfirm changes

Inline edits are staged, not applied. Change a name, a key or a lead and the row is marked Unsaved, with an Undo this change beside it. Nothing reaches Jira until you click Confirm changes and read the from-and-to list in the dialog. That is the review step, and on this tool it is the only thing standing between a mistyped key and every issue in the project being renumbered.

Bulk action	What it does	Reversible?
Change Lead	Sets a new lead on the selected projects.	Yes, set it back.
Transfer Lead	Moves lead ownership from one person to another across the selection. The bulk version of somebody changing role.	Yes.
Archive	Archives the selected projects, hiding them from normal use.	Yes, with Restore.
Restore	Brings archived projects back. The table has an Archived filter to find them.	Yes, archive again.

The most useful filter here is “Never updated”

Projects that were created and then forgotten. They keep consuming schemes, fields and everyone's attention in project pickers.

Changing a project key rewrites every issue key

Jira redirects the old keys, but every external reference sees the new one: bookmarks, wiki pages, tickets in other systems, scripts that match on the prefix. Treat a key change as a communications task, not a settings tweak.

Project Activity

What it does. Counts issue creation per project over the last 12 months and sorts every project into a band: Active (3mo), Moderate (3–6mo), Low (6–12mo) or Dormant. Searchable, sortable and exportable as CSV.

Admin Toolkit → Project ActivityIllustration

Project Activity

Export CSVRe-scan

Issue creation activity across all projects over the last 12 months. Last scan: today 07:40 UTC.

142

Total Projects

Active (3mo)

Moderate (3-6mo)

Low / Dormant

Project	Issues Created (12mo)	Last Active	Status
Operations (OPS)	4,182	today	Active
Support (SUP)	2,904	today	Active
Marketing Site (MKT)	94	4 months ago	Moderate
Legacy CRM (CRM)	0	2 years ago	Dormant

Run this before any configuration cleanup

“Is this scheme still needed?” really means “is any live project using it?”. Once you know which projects are dormant, most cleanup decisions stop being a judgement call. The CSV export is also what you send to project owners before you archive anything, so nobody is surprised.