Hello everyone!
We have set up an automation rule to handle "backport" issues (cloning an existing work item/issue to a past version). This rule uses a manual trigger with checkboxes so users can select the specific version(s) where the issue needs to be reported.
Here is a look at our current workflow:
The Problem: The clone action sometimes fails. This usually happens when users try to backport older issues that don't have certain fields populated—fields that have recently been made required in our project.
Our Current "Error Management": Right now, we have a very basic workaround: we use a JQL condition to check for all potentially missing required fields. If it matches, a customized email is sent containing a static list of all possible required fields.
However, this list is growing way too long. Users now have to sift through a huge list of fields (most of which are actually populated) just to hunt down the single one that is actually missing.
My Question: Is there a way within Jira Automation (perhaps using smart values, variables, or conditional blocks) to check exactly which fields from a specific list are empty, and then generate a dynamic email reporting only the missing ones?
Any advice, workarounds, or best practices on how to achieve this would be greatly appreciated!
Thanks in advance!
Automation by default don't have validators for Manual trigger action and I believe that this can be hard to do.
I would go with completely different approach. Run a script to find all tickets without all necessary fields and based on list fix it.
Regards,
Seba
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.
In this scenario you don't have to use automation. I thought to run script outside Jira which user rest api to get results that you are looking for.
Seba
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.