saltrock

Burning down the boomerland of tech

[saltrock @saltrocklabs]

Forge SQL won't wrap a multi-step write in one transaction. So any Forge app that writes more than once has to plan for a crash halfway through. Ask your vendor how theirs handles it.

[saltrock @saltrocklabs]

Project request approved. Project created. Permission scheme never applied. Now what?
If your Jira provisioning can't recover from a half-finished run, it isn't automation. It's a coin flip.
We scope that problem at https://t.co/QUpyyLqLou

[saltrock @saltrocklabs]

Pop quiz: is "is blocked by" the inward or outward side of a Jira link? If you had to look it up, so does every script and report built on top of it. Plenty of them get it backwards.

[saltrock @saltrocklabs]

Quick weekend audit: open your Jira permission schemes and check who actually holds Delete Issues. Groups, project roles, one-off users. It's usually a lot more people than anyone ever signed off on.

[saltrock @saltrocklabs]

Since March 2026, every install of a Forge app shares one Jira API budget of 65,000 points an hour. If your Marketplace app works for 10 customers, ask whether it still works for 500.

[saltrock @saltrocklabs]

Shipping one release across five Jira projects means five versions with the same name, kept in sync by hand. Somehow that's still normal.

[saltrock @saltrocklabs]

Jira lets anyone link anything to anything, across any project, with zero rules. Then someone builds a dependency report on top of it and wonders why it's garbage.

[saltrock @saltrocklabs]

Jira Cloud still has no recycle bin. Delete an issue and it's gone for good. In 2026.

[saltrock @saltrocklabs]

If ONLY one person on your team knows how to set up a Jira project, you don't have a process. You have a single point of failure.