Global Checklists are currently in BETA and will be available in Issue Checklist for Jira ENTERPRISE once released. Contact our support team if you currently use Issue Checklist for Jira PRO would like to participate in the Beta.
This page lists all the bugs and feature requests on Jira / AC backlog that impact Checklist for Jira:
AP.history race condition - https://ecosystem.atlassian.net/browse/ACJS-1155
New Issue View panel position - https://ecosystem.atlassian.net/browse/ACJIRA-1561
/installedwebhook before creating issue custom fields - https://community.developer.atlassian.com/t/atlassian-connect-express-the-enabled-webhook-is-called-before-jiraissuefields-are-created/58102?u=faridkhaheshi
Skip notification entries when updating custom fields (checklist): https://jira.atlassian.com/browse/JRACLOUD-77781
Override screen security when creating issue: https://jira.atlassian.com/browse/JRACLOUD-76451
Project condition not working: https://ecosystem.atlassian.net/browse/ACJIRA-2596
Create subtasks dialog: https://ecosystem.atlassian.net/browse/ACJIRA-1487
Entity property custom fields are not updated on the board immediately after issue/entity property is updated: https://jira.atlassian.com/browse/JSWCLOUD-22034
Jira built-in RegEx validator cannot access custom fields added via the descriptor.
AP is not defined
This problem happens intermittently and page reloads usually fixes it. It might present to customer in various ways from app frame not loaded (yellow triangle) to some functionality not working.
We can see this problem is recoded very often in Sentry but Atlassian does not track/admits it hence there is no public bug.
https://ecosystem.atlassian.net/browse/ACJS-1134 (it is not fixed; it still happens to us)
Cannot use JQL to search for incomplete items with exact text if statuses are disabled JRACLOUD-75866
Importing issues with CSV External System Import does not fire “issue created” event/webhook https://jira.atlassian.com/browse/MIG-378
Connect apps occasionally fail to load inside the Jira issue page views, with Atlassian Jira SPA (single page app) mechanisms fail to re-issue properly fresh jwt-token when user navigates back to already cached issue view. If you navigate back to an issue after 15min, the JWT will have already expired and the connection to the app will fail, causing an unauthorized error message. https://jira.atlassian.com/browse/JRACLOUD-81774 & https://jira.atlassian.com/browse/ECO-71