Optimize and fix

Optimize works out the corrected version of a flow, shows it beside the original, and gives you either a list of edits to make in Jira or a file to import. Other pages check what a change affects and tell the owners.

Optimize a flow

Open Optimize and pick a flow by name. Select Optimize. TuneCraft shows:

• Steps a month: now and with TuneCraft's changes (estimated).
• What to change: the changes TuneCraft makes itself ("TuneCraft makes this change") and the ones you make in Jira ("Change it in Jira").
• The flow as it is and corrected: the two side by side. Each change is marked Removed, Changed, Moved or Trigger changed.

TuneCraft changes a flow by itself only when the flow then does exactly what it did. It can, for example, set a trigger's "To status", limit a flow to one project, remove a step, move a condition up before a lookup, move a lookup out of a branch when its search does not use the branch's work item, and remove a re-fetch that reads nothing new. A few changes, such as moving a flow off "every edit" or replacing a search with the "Children" branch, are listed as changes to make by hand.

TuneCraft does not keep the texts of your flows, so it reads them from the export. Choose your export again when Optimize asks, or use the files you chose on the Scan page in the same tab. Your browser puts the real values back into the corrected flow: TuneCraft sees the flow without its secrets.

Edit in Jira or import

Optimize says which way fits.

Edit the flow in Jira when the changes are few. Editing keeps the flow's history.

1. Open the flow in Jira's automation.
2. Make the changes listed.
3. Save the flow.
4. Scan the export again. Saved then counts the fix.

Import the corrected flow when there are many changes.

1. Select Download the corrected flow. The file holds this flow only, with its real values, as Jira exports it. It can be up to 5 MB, the most Jira imports at once.
2. In Jira's automation, import the file. The flow arrives turned off.
3. Turn the original flow off, then turn the imported flow on.

TuneCraft cannot write a flow into Jira for you: Atlassian gives apps no way to create or edit automation rules. So the app always hands you the change and you make it.

Dependencies and Check impact

Dependencies lists the flows that can start other flows, and the loops among them. A loop is flows that start each other in a circle. Each run can start the next until a condition stops it, and every run costs steps. TuneCraft keeps at most 50,000 links and 50 per flow.

Check impact answers "what does a change to this flow affect?". Pick a flow to see:

• the flows it starts and the flows that start it;
• its loop;
• its copies, and the flows on the same trigger;
• the owners to tell, with their flows.

Run it before you turn a flow off or edit it. The list names at most 20 copies, so there may be more.

Copies and merging

When flows do exactly the same, the Copies of this flow panel names the one that stays and the copies to turn off once it runs in their projects. In shared projects every event runs each copy. A scheduled copy pays for its own runs wherever it is. Elsewhere a copy costs no steps, but it is one more flow to keep up.

The panel shows the steps to merge them in Jira, and Download the merged flow gives the file to import instead. It also warns you about:

• copies that do not run as the same person, because the merged flow runs as one of them in every project;
• a merged scheduled flow, which runs once for all the projects instead of once in each. Check that its search finds the work items of every project;
• who may edit it: only Jira admins can edit a flow that runs in several projects or in every project.

TuneCraft refuses to merge when the copies run on different sites, or together run in more than 100 projects. Merge those in Jira.

Tell the owners

Select Tell the owners to create one Jira work item for each owner, in a project you pick, as you. Jira then emails each owner, and they can comment on the work item.

1. Pick a project every owner can see: Jira tells only people who can browse it.
2. Pick a work item type you can create there.
3. Say what will change and when it is planned.
4. Confirm Create work items.

The work item names the planned change, the steps it saves (estimated) and the owner's flows the change can affect. TuneCraft keeps which work item told whom and when. The text stays in Jira. Told before shows earlier notices. Project admins can send notices for their own project only if a Jira admin allowed it in App access.

If Jira does not confirm the work items, the page says some may have been created and asks you to check the project before you send them again.

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