Spaces

Spaces lists the idle and empty spaces of your site and the flows that still run there, and also stale versions, components no work item has and categories no space uses. It reads Jira and changes nothing.

On this page

Before you start

Spaces is for Jira admins. A Jira admin turns on its background checks in Spaces settings. TuneCraft then reads every space, live, archived and in the trash, then each space's components, weekly where the site's points allow and less often on large sites. The first reading starts within the hour and takes a few hours on a large site. Spaces settings also set how many months make a space idle (3, 6, 12 or 24; the default is 6) and when a version is stale.

The Spaces page

The page opens with summary tiles. For each space it shows its state (live, archived or in the trash), its last work item update, its work items as Jira counts them, whether it is team-managed, its lead and whether the lead's account is active, and the flows of the last scan that run in it or name it, with their steps a month. The lead is read when the page opens and never kept. You can filter, sort and download the list as CSV.

  • Empty: no work item.
  • Idle: no work item updated for the months set in Spaces settings. Archived spaces and those in the trash are neither.

Idle or empty is what Jira's counts say, not proof that nobody uses the space. Beside the advice the page says what it did not check: boards, filters, dashboards, plans and a service space's portal. An empty space may also be new.

The flows that still run there

The flows come from the last scan of your automation export. A flow that runs only in a space fails once that space is archived: turn it off first. The advice counts the flows that run only there: for example, "Archive it and turn off these 3 flows first: about 1,200 steps a month (estimated)". TuneCraft cannot turn flows off. Jira's automation does that, and Check before you delete shows who owns them.

Versions

Versions lists stale versions in the spaces with over 500 versions. A version is stale when it is:

  • unreleased and 90 days past its release date;
  • released over 12 months ago with no unresolved work item;
  • on no work item (as its fix version, affects version or in a version field).

The days and months are settings. Archived versions do not count toward Jira's cap of 15,000 releases a space. TuneCraft reads those spaces' versions weekly. To see any other space's versions, pick the space: TuneCraft reads up to 500 now, as you, within this hour's points for work you start, and keeps nothing.

Components

Components lists the components no work item has, as Jira counts them. Jira has no archive for components, so these are the ones to delete. Compass components are not counted. Delete them in the space's settings after checking their flows.

Categories

Project categories that no space uses, live, archived or in the trash, are on the Spaces page. Delete them on Jira's categories page.

What Spaces does not do

Spaces does not archive, trash or restore spaces, and does not change versions or components. Do those in Jira. It does not check filters or read plans.

What it keeps

For each space: its id, state, last update day and category id. For each component: its id and work items. For the spaces with over 500 versions: the versions' ids, states, release days and counts. No name and no lead. Names are read from Jira when you open a page. If you turn the checks off, what they read is removed within a day.

Questions about the app? Write to info@plugincraft.ca.