Unable to add checklist template to new issue created in Jira Service Desk automation

[Jesse Morales]

Hi 

I am receiving an error when running an automation with the Checklist plugin app, I have copied the same rule details from our production company managed project to our sandbox project. Our rule details goes When: Issue Is Created > Issue Type Equals > Then Edit Issue Fields > Choose Fields to set.. > Checklist Text

When creating a ticket I receive the following error:


Action details:

Issue condition

The following issues passed:

IT-0000

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):

IT-0000

I created a template within the Checklist app and since it is in a different org (company.sandbox.atlassian.net). we do not see the other templates from our production org (company.atlassian.net) are there any schemes or fields that would need to be changed or updated to get the Checklist template added to the new issue tickets that get created in our service desk? 


Thanks!

[Jesse Morales · Accepted solution]

Resolved: Jira's built in automation is not the way to add a checklist. 

Best and most sure way to add a checklist is through the Checklist page itself, make a template and set it as default for Issue Type and Request Types. 

[Polina Zarnitskaya]

Hello! Have the same issue. 

I need to add checklist upon creation of specific task. Not to all tasks . Is it possible?

[Jesse Morales]

Update, was able to confirm that the field name was Checklist Text (migrated) 

Rule is now able to show success but not seeing any text being updated in the ticket. Will need to investigate this part. 

[Wojciech Wardaszko]

Hi @Jesse Morales

It's not clear which Checklist app you're using, but if it's by chance our Issue Checklist for Jira Pro or Free, I can tell you what to do. I think it is the app in question, since the template functionality you described in your solution matches our interface perfectly.

If that's correct, to use automation with checklists you first need to enable the Save Checklist data to Jira custom fields option in the Issue Checklist Global Settings (available through Manage Apps menu) for any automation to work. Please note that due to Jira limitations multiline custom fields are currently unavailable in next-gen (team-managed) projects. Hence, it's impossible to use automation with the Checklist Text field in those projects.

You will also need to verify that you only have one Checklist Text custom field - it looks like you migrated your Jira Cloud instance and can now have duplicated custom fields. I'd advise removing the extra custom fields with the (migrated) suffix. and only leaving the six custom fields our app uses, as listed here.

Let me know if this clarifies the situation a bit.

Cheers!

[Samuel Francis]

Good morning!

I have run into the same issue.  This would be similar to creating components for one jira project, populating the issue with the component(s) and moving to another project that does not have the same components available.   Therefore, it will look like the components have been remove or does not show.  There are still there, but are unable to be displayed.   I believe the same is happening here.  The checklist is there, but you are unable to view it.   You can use JSON within the automation.  However, you will need to know the field ID and list position of the checklist item you are trying to access.   Even then you may only get a raw list instead of the actual checklist.   If I can figure this out, I will post the answer.

Kind Regards,

Samuel Francis