Tootfinder

"Tree! Document <title> is wrong! Specifically this <valueX>! Who is the ignoramus who specified that value? ITS COMPLETELY WRONG WHO DO I GET TO LIGHT ON FIRE AND BLAME FOR EVERYTHING BEING WRONG?"
<checks Jira tickets that produced the latest document revision; goes back 3 document revisions over as many years>
You did. See here (2 yr old ticket): "pls change valueX from <blah> to <blah> because <rationale>. "
"…

Ich sollte meinen CorpoStack (bzw. neuer Name wird vermutlich KMU!Suite) mal flott machen, dass ich ihn zum nächsten Digital Independence Day präsentieren kann.
im Anhang ein Screenshot. Ich schreibe hier mal die alternativen hin:
- Jira Confluence -> #OpenProject
- Github GH-Actions ->

Jira is clearly not made for software engineers.
It hasen't been when it was in use at previous jobs, and it isn't now in 2026.
Edit: Gemini agrees.

RAG4Tickets: AI-Powered Ticket Resolution via Retrieval-Augmented Generation on JIRA and GitHub Data
Mohammad Baqar
https://arxiv.org/abs/2510.08667 https://

RAG4Tickets: AI-Powered Ticket Resolution via Retrieval-Augmented Generation on JIRA and GitHub Data
Modern software teams frequently encounter delays in resolving recurring or related issues due to fragmented knowledge scattered across JIRA tickets, developer discussions, and GitHub pull requests (PRs). To address this challenge, we propose a Retrieval-Augmented Generation (RAG) framework that integrates Sentence-Transformers for semantic embeddings with FAISS-based vector search to deliver context-aware ticket resolution recommendations. The approach embeds historical JIRA tickets, user comm…

Designers are always inventing new titles. Web designer, UI designer, UX designer, UX/UI designer, Product designer, UX/AI designer (???)
These are all the same!
As long as your work is mediated entirely by Figma and Jira, you are just a production artist.
Fighting with PMs over who "gets" to do strategy (usually: neither of you) won't help you. Lean into the core #design

Without UX governance, your app turns to "sludge"
Break out of the feature delivery mindset and attend to the architecture and maintenance of the product.

Titan submarine: Also in the same ntsb set of documents are a) The interview with the Softee who worked on some of the software, (describing Jira and Git to marine investigators..), and replugging the Logitech joystick dongle, and who had also got into screwing the end cap of the sub on and torquing the bolts up (!).
and b) The details of the recovery of the images off the camera - which turn out to be useless - but involved some fun with Luks, and a Qualcomm SoM.

En Australia han implementado el control de edad para acceder a servicios on-line. Desde hoy los menores de edad no pueden acceder a Jira ni a los servicios on-line del gobierno australiano.
JAJAJAJAJAJA

A recurring issue:
Source of Truth vs Point of Truth with many-system setups.
Imagine having separate
- issue tracking (e.g. JIRA)
- time tracking (e.g. Toggl)
- development tracking (e.g. GitLab)
- daily team sync (e.g. Confluence)
- weekly sync with stakeholders (...)
Without diligent manual labor or a lot of handcrafted automation, those keep getting out of sync.

Why not switch your crappy software from crappy #SCons build system to even more crappy #Bazel build system over a patch release, call it "fully backwards compatible", and then effectively leave all the distros stuck on old versions with half a dozen vulnerabilities?
Yeah, just a random reminder that #MongoDB is total crap, and you shouldn't use it. Or expect people to package it for you.
#Gentoo

“in an effort to streamline productivity we moved the button that is the raison d’être of Jira into a new location where it's really easy to _not_ see it”
Someone at Atlassian, probably.