nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Checklist Text not working from a Jira automation

Sérgio Baixo

Hi all,

We have an automation that simply adds a Checklist Text list to a certain issue. However, when that automation is executed, it does not write the list, even though the automation results in Success. If on the other hand I manually paste the list into the Checklist field in a certain issue, it works and I can see the complete list. I'm adding attachments to help understand the problem. Any form of help is welcome!

Regards,

Sérgio

Accepted answers

Gracjan Wesołowski _HeroCoders_

Hi @Sérgio Baixo

My name is Gracjan from HeroCoders, the company behind the Checklist app.

Can you show me what exactly you can see in the audit log of that automation? Is edit issue successful?

To work with the Checklist Text custom field, you have to enable the Save local checklist items to Jira custom fields option available in Jira Settings>Apps>Global Settings under Checklist for Jira app. Is it enabled?

Cheers!

Gracjan

All comments

Gracjan Wesołowski _HeroCoders_

Hi @Sérgio Baixo

My name is Gracjan from HeroCoders, the company behind the Checklist app.

Can you show me what exactly you can see in the audit log of that automation? Is edit issue successful?

Cheers!

Gracjan

Bill Sheboy

Hi @Sérgio Baixo

Adding to the suggestions from @Gracjan Wesołowski _HeroCoders_ ...

Please also show the entire Edit Issue action in your rule. It appears to also be making a change using the advanced edit with JSON feature and perhaps there is a problem with the JSON expression.

Kind regards,
Bill

Sérgio Baixo

Hi @Bill Sheboy

Thanks for your reply. The issue was that the wrong Checklist Text ID was being called inside the automation, and since it had been deleted in the custom fields while another Checklist Text with a different ID was there, it became misleading to trace the cause of the problem. But it has been fixed now

Sérgio Baixo

Hi @Gracjan Wesołowski _HeroCoders_

Thanks for your support and for quickly being able to solve the problem.

Best Regards,

Sérgio

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud