Hi, I see I can enable workflow in an app via a type extension. A couple of questions on this:
- what’s workflow linked to then, the type? Or, each board?
- one can use a custom field as columns in a board, so what is special about having a workflow? What will be able to do with it, if it’s an extension as opposed to if it were just a custom field?
I’m thinking about how workflow needs to be different depending on process. For instance if I have a normal support ticket, the flow might be:
- New
- Next
- Working
- Waiting
- QC
- Done
- Dupe
- Cancel
Then sometimes, in the process of doing some IT support task, like “fix my slow computer” you decide to change something on the system like upgrade memory, and so, need more of a change control process:
- New
- Not authorized
- Ready
- Plan
- Deploy
- Early life support
- Success
- Backed out
In that case, I was wondering if the way to handle this is make an app like Tasks, maybe called Changes and set the workflow differently on it? Then, maybe a custom action button could be on the Task, like “Initiate Change”, which copies some important stuff from the Task, and makes a new Change item based on that.
What’s the best approach here?