[rektide]

I worked at a data-warehouse company once that made incredibly good use of Jira for orchestrating their pipeline/data-flows. 80% of the purpose of the company was collecting, ingesting, & cleaning up a huge number of pretty dirty data-streams, often by calling people & having them send us files or sometimes disks. Some really rough data, & we had multiple automated & physical processes, & needed different people to sign off on different stages.

The whole system was built around Jira & performed wonderfully. Jira governed all the data-flow through the system. Each ingest was a ticket, and tickets would move from one stage to the next (Across the swim lanes) through over a dozen steps, some automated, some manual. Signing off was just the person with the role to move the ticket to the next column doing so. If the pipeline hit a snag, it turned red via a label & some js. Jira ran that company, was it's workflow engine, and it did a great job.

Not the day-to-day developer experience, but it left a huge mark on me; radically shifted how I view software, how I view workflows, made me rethink of Jira from a way to ship code into something far more generic & capable, if the need arises.