We update to ScriptRunner for Jira 5.3.26 when it was release and have a user that says the issueFunction in addedAfterSprintStart is now generating different results. When specifying a board and sprint it looks to be only including unresolved issues. Is this the intended behavior that has changed or has it always been this way? We didn't record what version we were on before the update, but I believe it might have been 5.2.2.
Version 5.4.11 of ScriptRunner for Jira included a fix for our issue with issueFunction in addedAfterSprintStart.
I also opened a support ticket with Adaptavist for this issue and there is now a development ticket created, SRJIRA-2852. It is currently just in the Triage status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
support request done to Adaptavist https://productsupport.adaptavist.com/servicedesk/customer/portal/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I saw same problem also Running JIRA v7.3.8 + latest ScriptRunner.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.