The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

In Assets/Insight automation the Execute Groovy script action does not recognize Windows path

ThangTN8
December 4, 2023

Issue Summary

In Assets/Insight automation the Execute Groovy script action does not recognize Windows path. 

Steps to Reproduce

  1. Install Jira Service Management 5.11.2-REL-0001 (or any other affected version listed above) on a Windows machine. 
  2. Create an Assets/Insight schema;
  3. On this schema configure an Assets/Insight automation with the Execute Groovy script action;
  4. Enter the absolute Groovy script location in the File path field;
    Example:
    C:\Program Files\Atlassian\Aplication Data\Jira\scripts\somefile.groovy
  5. Save.

Expected Results

Automation will successfully save without any error.

Actual Results

We see the following error on the UI:

Capture.JPG

=> Script file path must be absolute

 

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Marc -Devoteam-
Community Champion
December 4, 2023

Hi @ThangTN8 

Welcome to the community.

I think you are running into the following issue mentioned in JSDSERVER-12219.

One of the work arounds should help you, for the time being.

ThangTN8
December 4, 2023

@Marc -Devoteam- Thanks you very much ! 

Like Marc -Devoteam- likes this
ThangTN8
December 6, 2023

@Marc -Devoteam- I tried but the automation rule couldn't read that groovy file.

I put my groovy file in: C:/Users/thangtn8/Atlassian/Application Data/Jira/scripts/update_attribute_value.groovy

Is the location of the file wrong?

 

Marc -Devoteam-
Community Champion
December 6, 2023

Hi @ThangTN8 

See the liked issue and take the steps described in WO 1 or WO 2

There is nothing wrong with your path, but it is not recognised an there is nothin wrong with the location.

Please read the information on the issue linked in my previous post.

DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events