Breaking Changes
Check out these breaking changes for updates that could affect your instance.
Migration of admin pages to Forge
We have migrated ScriptRunner for Jira Cloud admin pages to Forge!
All of your data will remain unaffected and accessible. Other than the following updates, ScriptRunner for Jira Cloud features function the same, and there is no removal of features. We have a couple of changes in how you access ScriptRunner for Jira Cloud and Enhanced Search:
Action Required: Update your bookmarks
Administration page URLs have changed since migration. Please update your bookmarks for any administration pages you have saved.
To learn more, please visit the Release Notes.
JQL Parsing Updates
Atlassian's Jira Cloud search now strictly enforces valid JQL syntax and operators. Invalid JQL clauses will return in zero results. Previously, some invalid JQL clauses were handled and could return partial or lenient results, which created inconsistent search behavior. Jira Cloud is now handling these invalid JQL cases like Jira Data Center and follows the JQL documentation. This change is not backwards compatible. Invalid syntax or operators that were previously in use will now receive zero results for those clauses, instead of partial or lenient results.
For example, issuetype = ("Task", "Story") uses the incorrect = operator. It should be issuetype IN "Task", "Story").
How Enhanced Search is impacted
Enhanced Search runs initial parsing checks, but it will not catch every server-side validation rule enforced by Atlassian. If you notice that your searches that previously worked are returning zero results, please review your JQL and ensure it aligns with the Atlassian JQL documentation. We anticipate the most impacted clauses will be due to incorrect operators.
What you need to do
To ensure your searches continue to function correctly, please review and update any saved queries or automated JQL strings that you rely on within Enhanced Search. If a search is failing, we recommend copying your JQL directly into Jira's native advanced search bar, which highlights any syntax errors that need to be corrected.
Advance notice: Enhanced Search for Jira Cloud migration to Forge
Enhanced Search for Jira Cloud is moving to Atlassian's native Forge platform this year. As part of this transition:
- Searches will be integrated into the native Jira search bar.
- Forge custom JQL functions will be used.
Watch this space for further announcements on dates and deadlines.
What you need to do before migration
We will initiate the transfer of your filters according to a planned migration schedule. Any filters that fail to migrate automatically will remain on Connect for you to fix before you can manually attempt to migrate it again.
To avoid disruption during the rollout of the new app version, you must identify any existing saved filters that require attention to ensure a successful migration from the current Connect platform to Forge.
Detect broken filters
If a filter requires attention, an error symbol indicator appears alongside it. This indicator:
- Highlights filters that are at high risk of failing during migration.
- Includes a link to additional information about the issue.
For example, you can see all error symbol indicators contained within the image below:
There are two new limits associated with the Forge migration:
- Result limit of 1,000 issues
- Timeout limit of 25 seconds
Both of these limits are per precomputation. A precomputation is an individual use of an Enhanced Search function. Filters can contain multiple precomputations, and each one can return up to 1,000 issues and run for 25 seconds.
Example: issueFunction in linkedIssuesOf("project = test") and issueFunction in addedAfterSprintStart(1). Each use of a function, or precomputation, can return 1000 issues, so the entire filter could return 2,000 issues since there are two. For timeout limits, each function, or precomputation, can take 25-seconds to process. They will run at the same time.
Each symbol relates to a different error type that include:
- Results exceeding 1,000 issues:
- Taking 25 seconds or longer to load:
- Returning errors:
Once the issue is resolved, the indicator will disappear.
How to fix broken filters
You must review and update your saved filters that have been flagged with an error symbol. Refer to the Troubleshoot section for guidance on resolving filter errors or other issues.