<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Workflows on Bootstrapping.org</title>
    <link>https://bootstrapping.org/tags/workflows/</link>
    <description>Recent content in Workflows on Bootstrapping.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bootstrapping.org/tags/workflows/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Helpdesk Ticket States: Renaming a State Under Open Tickets Without Moving One</title>
      <link>https://bootstrapping.org/helpdesk-ticket-states-renaming-a-state-under-open-tickets-without-moving-one/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bootstrapping.org/helpdesk-ticket-states-renaming-a-state-under-open-tickets-without-moving-one/</guid>
      <description>&lt;p&gt;Workflow states are reference data with consequences. A helpdesk ships states like new, open, resolved and closed. Every ticket points at one, and each state names the one that usually comes next, so the application can offer a &amp;ldquo;move on&amp;rdquo; button. Renaming a state, or adding one in the middle, is a release-day job that usually ends in a hand-written migration.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://github.com/bootstrapping-engine/bootstrapping/tree/main/examples/workflow&#34;&gt;workflow example&lt;/a&gt; does it with seed files. The states table refers to itself: &lt;code&gt;next_id&lt;/code&gt; holds the id of the next state, and the seed writes it by code.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
