Introduction

For each project there are a number of key things which are configurable on a per-project basis.

The Project Settings Summary screen gives a good summary of that.

Open

Investigation

So here are the different types of things we will focus on:

• issue type scheme

• Workflow schemes

• Screen Schemes

• Issue type screen schemes

Trying to figure out why there is proliferation of schemes everywhere.

Problem statement

Why does it not cross out the Jira when I move something to Verified using my “Software Simplified Workflow Done + Verify” Workflow.

This has to do with the Workflow Scheme (Workflow is the statuses of the lifecycle of a Jira item in Jira)

Workflow Schemes

The theory

It’s done in Settings → Jira Issues → Workflow schemes

Then you have to update the board settings.

Why does Jira keep creating new schemes?

When I try to change the Workflow scheme of my project this shows up. WTF?

Open

Hypothesis

Every time you create a new project, Jira creates a new scheme…. For all issue type!……

What is a scheme for?

For permissions, the scheme allows to bind privileges to roles. It's a mapping table.

But for workflows?
You can find all the schemes if you go to Jira Settings → Issues

The answer is: it allows mapping between issue types and workflows. 💡

Now it looks like this:

Open

Okay so some progress has been made by deleting a lot of useless schemes. There were hundreds of them.

So that different types of Jira “things“ can have different lifecycles. It’s just a routing table. so now to the next thing

Okay so this is a compound problem.

At the first level you have “Jira creating new Workflow schemes for no fucking reason every time you create a new project” problem.\

Then you have the actual “how do I link a status to a Resolution“ problem. In other words how do I get that tickmark?

Open

Seems like there is a retain cycle in the Atlassian software. Every new project gets a scheme. So that makes that scheme active. Remember a scheme is something that binds issue type to a workflow (mapping table). You can change the workflow scheme from the project settings so there is no retain cycle.

It seems we need to go at a higher level. We need to go to the place where the Workflows are defined (not at the project level). Where is that place?

It’s Jira Settings → Jira Issues (NOT Confluence)

This is the Gibson right here:

Open

Why do new projects automatically create a new Workflow Scheme????? It makes no sense.

They also create a new Workflow by the way, so you can repeat the “delete all the things” exercise in the Workflow menu of Jira → Settings → Issues.

Finally the answer to the original problem statement can be found in the Workflow editor (same location). When you create a new status it asks you which category you want to associate it with. If you chose “Done“ then it gives you the tickmark.

Open

Selecting Done doesn’t give you the tickmark, what gives you the tickmark is adding a post-function to the transition to that status. The post function should be “Update issue field” and from there you can update the “Resolution“ field to the Done resolution. This is what gets you the tickmark.