Labels

Labels lists every label Jira has with its work items and the flows that check or add it, finds labels that are copies, and renames, merges or removes a label across its work items. TuneCraft keeps no label's text.

Before you start

Labels is for Jira admins. There is nothing to set up: the list is read from Jira, as you, each time you open the page, and TuneCraft keeps none of it. To see which flows use a label, scan your automation export first.

The Labels page

Use Find a label to search. For each label the page shows the work items Jira finds with it, and the flows of the last scan that check or add it.

• The work items are Jira's count of a search for the label, made as you. Work items you cannot browse are not counted.
• Jira's search finds a label in any case, so Release and release are counted together. Where the page knows a copy by case, it says "about".
• Jira does not search archived work items. A label that Jira lists with no work item found is on archived work items only, or on none.

Label copies

Label copies groups labels that are equal except for case, or one letter apart when they have 5 letters or more. It reads every label Jira lists, up to 10,000. Shorter labels one letter apart, such as v1 and v2, are often different words and are not grouped. A digit never counts as the letter apart, so sprint-1 and sprint-2 are not copies. Pick the label to keep in each group, then merge the others into it.

Rename, merge or remove

You can rename a label, merge it into another, or remove it from its work items. A rename to a label that already exists is a merge.

1. Choose the change. TuneCraft shows a preview with the work items it found and the flows the edits would wake, with their steps (estimated). Flows that start when a work item is updated, or when its labels change, may run for each edit.
2. Confirm. TuneCraft searches the work items with the label and edits each one as you, without Jira's email.
3. The page shows the progress. The change runs while the page is open and waits when the hour's Jira points are spent. Carry it on later from Changes with its record file.

Details:

• Each work item costs about 2 Jira points (measured). 50,000 work items take about 100,000 points, about 2 days within your hourly points.
• A change keeps to the work items its preview found. It does not start when Jira now finds more than the preview's count plus a margin of 10 work items or 2%, and it stops once it has handled the count it started with and that margin.
• Jira lets no one edit a work item in an archived space. Those work items are counted and left.
• When Jira gives no clear answer to an edit, TuneCraft reads the work item's labels again before it carries on.
• At the end, TuneCraft looks for the label once more. If a flow or a person keeps adding it, the change stops and says so.
• Choose Pause, then Stop here to end a change where it got to. It is recorded as stopped.
• Flows that check or add the old label keep using it. Change them.

The record file and undo

Because TuneCraft does not keep label text, the record file holds the labels of a change. It goes to your computer. Changes asks for it to carry a change on or undo it.

You can undo a change for 30 days, counted from its start. TuneCraft checks the file's labels against its record, then puts the old label back and removes the new one, only on the work items the change edited. An undo that cannot edit some work items ends partly undone and says how many it left. Undo again from Changes to give back the rest.

Only the person who started a change or an undo can carry it on. Any Jira admin can start an undo, recorded under their own name.

What it keeps

For each change, TuneCraft keeps its labels as keyed hashes, its counts, and the ids of the work items it edited (30 days). It keeps no label's text.

During a trial, every report works, this tool makes at most 10 changes, each on 1,000 work items at most, and an undo is not counted. See Licence and trial.

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