Error on Added after sprint start flag Version: 3.0.16.

ScriptRunner 3.0.16.
In a planned sprint on Agile board backlog, click the Added after sprint start flag
We are now getting error:
  • No Board with that name could be found.
  • No signature of method: com.atlassian.greenhopper.service.rapid.view.RapidViewServiceImpl.findRapidViewsByName() is applicable for argument types: (com.atlassian.jira.user.BridgedDirectoryUser, java.lang.String) values: [LGariep1:10000, CAMS Dashboard]

Can you help?

5 answers

Hi Jamie,

 

I modified the board name, and the clicking on the flag icon still gives the query error that board name is not found.

 

What is the "other problem" you've mentioned that might be causing this?

The one mentioned above: No signature of method...

Ok, I thought name not found and signature not present would be one and same, and modifying the name would update the signature as well. Thanks for clarification, would wait for 3.1.4 for the resolution. (just for reference, I checked in v 3.1.3)

0 vote

This is going to be fixed in the release after next, which should be 3.1.4.

When you click on the flag icon it's not getting the right name for the board... but if you modify the board name it should work. If it doesn't, due to that other problem, that also will be fixed in the upcoming version.

Jamie,

We just updated to version 4.1.3.9 and we still get this error for any of the Sprint functions:

 

  • Cannot get property 'value' on null object
  • No Board with that name could be found.

I tried with any of the boards name we have and it does not work

Would really appreciate some help in resolving this.

 

Robert

 


What version of JIRA and JIRA Agile?

Hi there

I have the same issue. I run Agile 6.7.12 and JIRA 6.4.7

Roughly when can a fix be expected? My very useful "Scope Creep" Agile board filter, based on "issueFunction in addedAfterSprintStart()", is now broken...

it is fixed, the fix will be in the next version which I guess will be 3.1.4. I'm not sure when exactly... holidays approaching. You will need at least jira 6.3 though to upgrade to that.

Hello Jamie, We are are 6.4.6 and therefore ready to implement the 3.1.4 fix. Can you provide an ETA of when it will be available? Thanks, Lynn

Lynn, we are planning to release version 4.0 in or around the 1st September. Please note: this release will be a paid one. You can read our blog for more information about that: http://www.adaptavist.com/w/continuing-to-develop-scriptrunner-for-jira/

can this not be fixed in a pre-paid version as this is the only update we need to get it back to working as it was prior to the JIRA Agile board updates? This would be expensive for us to pay for just to get it back to working the way it used to

Richard, please contact us directly about this and our Sales team can discuss this further using this link: http://www.adaptavist.com/w/about/contact-us/

Hello,

 We are running v3.1.4 and are still having the same issue.


Was this fixed or will it be fixed in version 4.0?

Thanks

Chuck

Charles, Yes, this bug will be fixed in version 4.0 which will be released in the first week of September. Please note: this release will be a paid Add-on, the details are available in our recent Adaptavist Blog Post: http://www.adaptavist.com/w/continuing-to-develop-scriptrunner-for-jira/ Please note the compatibility in the FAQ (must have JIRA 6.3 or above and must have JIRA Agile 6.7.7 or 6.7.11): http://www.adaptavist.com/w/sr4j-4-faqs/

can this not be fixed in a pre-paid version as this is the only update we need to get it back to working as it was prior to the JIRA Agile board updates? This would be expensive for us to pay for just to get it back to working the way it used to

Richard, please contact us directly about this and our Sales team can discuss this further using this link: http://www.adaptavist.com/w/about/contact-us/

We are on 3.1.3-dc which is throwing the same error.  When can we expect to have a JDC version with the fix?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,210 views 13 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot