When tracking Workflows it would be very helpful to be able to add custom groups. The Not started, Started, Finished default groups are neat, but it would be amazing if we can change or expand them:
Here is our states in our product backlog. I would want to be able to have the following groups:
Blocked
Defining
Developing
Testing
Releasing
Live
Abandoned
Most of these groups would have 1–3 sub-states.
I can also imagine other workflows like approval processes and other to be wanting to support custom groups. I think that can still align with the isStarted and isFinished functionalities that you already have, but it might require a little re-jigging.
The existing groups are basically just hardcoded valies in a text field.
If you want your own categories, you can add a custom text field to the workflow ‘db’ and set the values appropriately.
The UI won’t be the same as the native groups, but the functionality will be.
Thanks, @Chr1sG, I’ve already added my own fields in some places, but as said, it would be neat if the Type would become a sorted single-select itself, so that the UI can also support it.
Yeah, so select fields (like the workflow) can’t themselves have select fields as properties.
I think if you need more than the ‘basic’ fields that a select database supports, then you would be better served by using a ‘full’ database instead of the workflow/select field.
There are obviously some differences in the behaviour/appearance of a select field and a man-to-one relationship, and there are a handful of discussions about these and related things, e.g.
but if these issues were resolved, I don’t see many drawbacks of using a db.
