Jira Is Turing-Complete (And You've Been Coding in It)
Jira has evolved from a simple bug tracker to a complex automation engine capable of Turing completeness. This means that users can create workflows that simulate computation, including loops and conditional logic. The implications of this transformation are significant for how teams manage their projects and automate processes.
- ▪Jira started as a bug tracker in 2002 and has since become a powerful automation tool.
- ▪It is now capable of simulating computation through its workflow and automation features.
- ▪Users can create loops and conditional logic within Jira, effectively programming within the tool.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3924862) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } BLNCraft Posted on May 25 Jira Is Turing-Complete (And You've Been Coding in It) #automation #productivity #devtools #discuss You didn't realize it, but the last time you built a Jira workflow, you wrote a program. A bad one, probably — no version control, no tests, no linter — but a program nonetheless. The Uncomfortable Truth About Jira Jira started as a bug tracker. A humble list of things that were broken, assigned to people who would fix them. That was 2002.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
