Topic hub

Jira

Administering Jira Cloud, and auditing what quietly broke.

§01

What this covers

One theme runs through nearly all of this: Jira told you it worked.

A form smart value writes nothing and reports success. A default value of None vanishes and takes the field's behaviour with it. sendNotifications does not suppress the notification. A filter keeps returning rows long after the field it references stopped existing. An attachment migration ships zero bytes behind an HTTP 303 that everything in the chain treats as fine.

So a good half of these are really about verification — checking that what you configured is doing what you think, usually with a query you can run yourself. Where the answer comes back as a count of zero there is normally a note on proving the query could have returned something at all. A broken query and an empty result look identical from the outside, and only one of them means you are finished.

§02

Series

Read in order

When Jira reports success

3 parts

What to check when a Jira rule or API call finishes without an error and the change never actually happened.

§03

Everything on this topic

Articles

TutorialCloud MigrationJira

Jira automation rules do not migrate themselves

JCMA brings your rules to Cloud disabled and without their actors. Cloud-to-cloud brings nothing at all. Measured on a live Cloud site: the Rule Management API's 400s that name no field, the app-actor discovery our own runbook got wrong, and the scope ARI the API silently rewrites behind your back.

Aug 19, 202618 min read

ArticleCloud MigrationJira

303 is not an error: how an attachment migration ships zero bytes

Jira Cloud answers 303, Confluence answers 302, and an SSO-fronted Data Center answers with a login page. I measured the two Cloud cases end to end, and the failure that follows passes every audit you are likely to write.

Aug 18, 202616 min read

ArticleJiraJira Service Management

One person, two JSM customer accounts: what actually clears the duplicate after an email change

A customer changes email domain and starts appearing twice in the reporter picker. Removing them from the project provably cannot fix it, the query that finds their tickets stays silent when it fails, and the reassign that clears them reports the wrong reason for refusing.

Aug 15, 202611 min read

TutorialJira

Clearing the Done column in Jira Cloud: company-managed vs team-managed

The manual Clear Done work items button is gone from team-managed boards, and company-managed boards never had it. They have something better, and I measured it: a released version empties the Done column for everyone in under 15 seconds.

Aug 14, 202612 min read

TutorialCogniRunnerAtlassian Forge

jira:workflowCondition vs jira:workflowValidator: one runs your code

We shipped both modules in CogniRunner pointing at the same handler. Only one of them ever invoked it. forge lint says No issues found, forge deploy validates the manifest and passes, and the gate you built is permanently open with zero log lines. Here is the probe app that proves it, and the two things that actually work.

Aug 14, 202614 min read

ArticleAtlassian ForgeJira

LeanZero Management: the Jira dependency that actually moves dates

A blocks link in Jira records a relationship. On Free and Standard it reschedules nothing. Here's the engine we put behind it, the required-start rule that's easy to get subtly wrong, and what it still can't do.

Aug 13, 202612 min read

TutorialCloud MigrationJira

Auditing a Jira Migration: a Wrong Field ID Counts to Zero, Not to an Error

Jira Cloud answers a JQL query about a custom field that does not exist with HTTP 200 and a count of zero. In a post-migration field audit, zero is the number that authorises deleting the field. I swept all 197 custom fields on a live site to find out which gate actually catches it.

Aug 12, 202616 min read

ArticleCloud MigrationJira

Your Jira filters survived the migration. That's the bug.

A saved filter is a string, not a binding. I measured what cf[10042] actually resolves to on a destination site, and where Data Center to Cloud and Cloud to Cloud each fail silently.

Aug 12, 202613 min read

ArticleJira

The Jira form smart value that writes nothing and reports success

A rule reads a dropdown answer off a Jira form, runs clean, logs no error, and leaves the field empty. Two things are wrong and both are in the rule rather than the log. Here is the mechanism, the full field-type mapping, and the check that decides whether any of it applies to you: there are two unrelated features called Forms and only one of them automation can see.

Aug 3, 202618 min read

TutorialJira

Suppressing the email when Jira Automation adds a comment (and why sendNotifications does nothing)

A Community Champion added sendNotifications: false to an automation rule, re-imported it cleanly, and still got the mail. Here is why the flag is ignored, which endpoints actually carry a suppression flag, and how to tell a real API parameter from one Jira is only pretending to accept.

Aug 2, 20269 min read

TutorialJira

How to Block Time Logging on Specific Work Types in Jira Cloud (Using Workflow Properties)

Your organisation uses Tempo Timesheets and needs to prevent users from logging time against certain Jira issue types — like Risk, Assumption, or any work type that exists for tracking purposes only. There's no toggle for this in Tempo. But there's a workflow property that does exactly what you need, and it takes five minutes once you know where to look.

Apr 9, 20265 min read

TutorialJira

The Jira Cloud Default Value Trap: When "None" Disappears and How to Get It Back

Set a default value on a Jira Cloud single select field and "None" silently vanishes from the dropdown — with zero UI option to bring it back. Here's what's actually happening under the hood and the exact curl command that fixes it.

Mar 11, 20265 min read

TutorialJiraJira Service Management

Microsoft Graph to Jira Assets User Ingestion

This comprehensive guide demonstrates how to build a robust user ingestion system that transfers users from Microsoft Graph API (Azure Entra ID) to Jira Service Management Cloud Assets. The solution handles complex scenarios without complete public API documentation by implementing custom logic for object reference attributes, user type attributes, and sophisticated error handling mechanisms.

Feb 1, 202630 min read