During migration testing we have found
Our MOVE Yoda suggested we consider implementing more complex logic via Automation instead of Workflow Validations. i.e. if the user transitions an issue but field data is not complete (or not valid), the automation rule would add a comment to the issue explaining the problem, and send the issue back to the previous status.
This approach cannot be used for Create transitions (new issues), but seems like it would be possible in other situations. However it seems a strange way to solve the issue.
Has anyone out there tried this approach?
Have your team found this UX logical/obvious?
I've seen these used - but I wouldn't suggest it's the best solution, it's a workaround.
I've found this can cause issues like...
I'd instead look for Apps which can extend validators from the Marketplace - such as...
...or look for other ways to meet your requirements.
If you have some specific examples of validation you need - happy to try to recommend a possible solution :)
Ste
Thanks for the observations. Hope these are helpful for others too.
We will need apps to get what we want, but I'm yet to work through all our workflows in Cloud to figure out the details.
It looks like differences between server and cloud apps will make this more difficult.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There are differences, but Apps are becoming more mature in Cloud as more teams move there.
Aside from taking the time to do the research, you could also contact App vendors and ask about specific needs, or ask for documentation comparing their Server and Cloud App functionality?
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.