In order for the user to start with default lifecycles when creating a fresh lifecycle , we need those from the backend so that they can be passed as is when doing so :smile: At some point we might want to introduce lifecycle templates, so we can leverage this terminology and create a query that returns lifecycle templates. Let's ensure we don't return IDs for statuses because we'll post them as names to the mutation and the backend will create statuses when they don't already exist.