Checklist text - automation failed

[Wojtek Szczerbinski]

Hi,
I'm experiencing an issue with automation that I created. It was working just fine but due to some problems in our organization, all of the automation rules must have been restored and since then this automation doesn't work anymore. 

I created an automation rule which adds a checklist to a ticket. 

Here is the flow:
When: value changes for Components 
Issue type equals: System Incident
Components contains any of: Here is the value we use
Then: edit issue fields - Checklist Text

But when I trigger this be editing the Components field I get the following error:

Action details:

Issue condition

The following issues passed:

RS-3786

Issue condition

The following issues passed:

RS-3786

Edit issue

Found multiple fields with the same name and type: .

Checklist Text (com.atlassian.jira.plugin.system.customfieldtypes:textarea)

No fields or field values to edit for issues (could be due to some field values not existing in a given project):

RS-3786

I checked in the custom fields and I see that we have 3 custom fields called Checklist Text, one of them contains the part (view-only) but in the description I can see: Do not delete. Custom field with Checklist content in text format. Automatically created and managed by Issue Checklist Free.

Is it possible that this issue is caused by the fact that we have two Custom fields with the same name?

Thank you

[Wojtek Szczerbinski]

Hi @Wojciech Wardaszko _HeroCoders_ 

After I deleted the other custom field the automation shows no errors but for some reason after the automation is triggered it doesn't edit the Checklist Text field inside of the plugin.

We are using the plugin called "Issue Checklist for Jira" and it works with a default template that I created but for some reason the automation doesn't affect it. 

What can we check?

[Wojciech Wardaszko _HeroCoders_]

Hi, @Wojtek Szczerbinski

You need to delete the one that has no information in Last used - you must have used another version of Issue Checklist in the past and that field is a leftover.

Once Checklist Text is no longer ambiguous, the automation will work as expected.

If you have any other questions or further trouble with automating Issue Checklist for Jira, feel free to ping me or reach out to our support team via our service portal. We usually reply within 4 business hours.

Cheers!

[Wojtek Szczerbinski]

That was it! I also noticed that I had to associate the custom field "Checklist text" with the proper project but now it works as expected. 
Thanks @Wojciech Wardaszko _HeroCoders_ 

[Wojtek Szczerbinski]

Ok so actually the automation itself works but the result I get it's not what is expected.
After I associated the Checklist Text custom field with the screen in the project it showed up as a separate element in the ticket and that's not what I want.

I want it to add the elements as elements in the checklist.
Like here:
https://docs.herocoders.com/checklist/add-checklist-based-on-a-custom-field-value

It's set up exactly the same way but for some reason when I trigger the automation it doesn't show up. 

It's important to mention that I noticed that we are using the plugin called "Issue Checklist for Jira" so I assume there is no need to associate this custom field with any screens? 

But how I can make it to add a new checklist through an automation? It was working fine in the past. 

[Wojciech Wardaszko _HeroCoders_]

Hi @Wojtek Szczerbinski ,

You are right - the Checklist Text field does not need to be on any screen to work as intended.

As for the automation not working, have you enabled the option to Save local checklist items to Jira custom fields? If not, those fields are not linked to our servers at all, they just wait, empty.

Once you enable this option, wait for our syncer to save checklist data from our servers to your Jira's custom fields (usually about 24h tops) and the automation should work without an issue.

You can refer to the current Checklists in automation with the {{issue.Checklist Text}} smart value, so you can add to what's already there if you need to, just put the smart value in a line above your new content in the Edit Issue action input field.

If you need any more help with that, please feel free to reach out to us (or me specifically) directly via our service portal.

Cheers!