Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Service schedule conflicts between xporter and scriptrunner/groovy Edited

Hi,

I've been working with scriptrunner for a while now and decided that I wanted to run one of my scripts as a service. So I setup my service following this and everything was fine until another add-on's schedule ran.

Every morning the add-on Xporter sends a report until today. Xporter  is set to run everyday at 9am and the groovy script is setup to run every hour. This morning Xporter silently died and my groovy script is now getting a nullpointerexception.

The script was running fine yesterday and it works in the script console, it's just the scheduled job that's having the issue.

When you re-create the groovy scheduled service in the GUI it works fine, it's like these schedules are sharing id's or handlers since they're running at the same time.

 

Any ideas on what could be causing these two schedules to fail?

 

Here's the stacktrace for my groovy script:

2019-03-13 09:00:07,158 Caesium-1-1 ERROR anonymous    Automated Ticketing Engine [c.o.jira.groovy.GroovyService] Script service failed: /path/to/script.groovy
java.lang.NullPointerException
	at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:210)
	at com.atlassian.jira.issue.attachment.CreateAttachmentParamsBean$Builder.build(CreateAttachmentParamsBean.java:218)
	at com.atlassian.jira.issue.attachment.CreateAttachmentParamsBean$Builder$build$4.call(Unknown Source)
	at org.projecthaystack.client.ticketEngine.takeScreenshot(ticketEngine.groovy:157)
	at org.projecthaystack.client.ticketEngine$takeScreenshot.callCurrent(Unknown Source)
	at org.projecthaystack.client.ticketEngine.run(ticketEngine.groovy:240)

 

 

1 answer

Hi Matt,

For similar situations, please open a ticket in our Service Desk so we can help you as soon as possible.

Our team is always happy to help!

Best regards,
Xporter Team

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

75 views 0 4
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you