Checklist Pro with automation is duplicating checklist items

[Michael Arndt]

I'm setting up some new recurring tasks using Checklist Pro along with Jira automation. I'm doing some test runs and each items on the checklist is showing twice. I'm unsure if this will occur when it's just running on schedule as I have these setup to run on Fridays and Mondays (starting next Monday). 

Is this a bug? I checked the YAML and don't see the duplication.

[Samuel Francis]

Good morning!

As mentioned above, you have to be careful when using a default checklist in conjunction with automation.   When setting up the default checklist, you will need to carefully choose what type of issues will fire/trigger the checklist.  The same must be considered when setting up automation for checklist.  Usually, the default checklist will override the automation.  However, if they are firing moments apart, you could very well see duplication.  I believe there are other checklist apps available that will allow for easier automation.   This would circumvent the need for setting a default.   

Kind Regards,

Sam

[Jack Hunter [HeroCoders]]

Hi @Michael Arndt,

To help, we would need to see your automation rule and how the duplicated checklist looks. 

Please share the screenshots here or send them to our support email support@herocoders.com according to your preference. 

Cheers,
Jack

[Michael Arndt]

You can see screenshots here https://imgur.com/a/M5eYWe1

I posted both the autmation setup page with YAML and also the issue screen. I only highlighted the specific duplicate's on one of the screenshots.

[Jack Hunter [HeroCoders]]

Thanks.

Could you please copy&paste the YAML here? Please use 'code block' formatting when pasting? We will test it on our side. 

Also, is there any other rule that updates the YAML field? 

Thanks,
Jack

[Michael Arndt]

items:
- text: '--- Natran checklist'
checked: false
- text: Review and sync Divvy
checked: false
- text: Review intercompany expenses
checked: false
- text: Add revenue into Quickbooks
checked: false
- text: Update company scorecard
checked: false
- text: Review expense transactions with no classification
checked: false
- text: Upload driver behavior scores
checked: false
- text: Upload Podium reviews
checked: false
- text: '---APS checklist'
checked: false
- text: Review and sync Divvy
checked: false
- text: Review intercompany expenses
checked: false
- text: Add revenue into Quickbooks
checked: false
- text: Update company scorecard
checked: false
- text: Review expense transactions with no classification
checked: false
- text: Run ServiceCEO payment report for "Other" payments
checked: false

[Michael Arndt]

No other rules.

[Jack Hunter [HeroCoders]]

Hi Michael,

I've just checked that the YAML provided is correctly transformed into the checklist.

There are two most likely reasons for your problem in that case:

• default checklist is used and not automation rule (or default checklist overwrites automation rule)
• there is some problem with your automation rule

Could you please reproduce the problem (create an issue and let automation add the checklist) and next:

• send us a screenshot(s) of full issue history
• send us a screenshot(s) of full checklist history

Thanks,
Jack

[Michael Arndt]

• default checklist is used and not automation rule (or default checklist overwrites automation rule)

I'm not sure what this means. Can you elaborate?

I'm still having issues. 

[Jack Hunter [HeroCoders]]

These are essential things to remember when using Automation or Default Checklist:

• Both the automation rule and default checklist are asynchronous tasks fired by Jira a moment after the issue was created.
• They are not aware of each other and they can be executed in random order (you cannot assume that Automation will be first all the time or vice-versa)

It means, that if your newly created issue was touched by the Default Checklist (some items added to the issue), and then the Automation rule is applied, it might completely overwrite the items added by Default Checklist. Several other/similar problems might happen when both are used and applied to the same issue.

Issue History and Checklist History should show exactly what happened. If you can provide us full/clean screenshots of these two right after the issue was created and the checklist doubled, we will be able to say more precisely what happened. 

Cheers,
Jack