Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,559,515
Community Members
 
Community Events
184
Community Groups

RemovedAfterSprintStart is not working in ScriptRunner 3.1.3

Hi,

 

We recently updated to ScriptRunner v3.1.3 (JIRA v6.3.1) and are unable to use the RemovedAfterSprintStart function.

 

Steps to Reproduce:

  1. Go to Issues -> Search for Issues
  2. Search using the following query -  issueFunction in RemovedAfterSprintStart(Scheduling, Scheduling-25)

Expected Result:

The Query returns all tickets removed from the Scheduling-25 sprint on the Scheduling Board.

 

Actual Result:

The following Error is returned:

 

image2015-7-14 15:37:9.png

We have tried with the Board Name in quotes and without quotes. Also tried with Sprint Name and Sprint Code. None of those worked.

We are using the correct syntax as suggested by the Syntax helper:

 

image2015-7-14 15:35:8.png

 

Same is true for the addedAfterSprintStart() function.

4 answers

Hi @Jamie Echlin [Adaptavist] - we are still waiting for an answer on this issue.

Hi @Jamie Echlin (Adaptavist), can you tell us why this is not working for us.

Hi,

 

Can someone look into this issue? In effect a bunch of commands part of the 3.1.3 upgrade are not working.

 

Arjun

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events