[JSDSERVER-12216] In Assets/Insight automation the Execute Groovy script action does not recognize Windows path

Type: Bug
Resolution: Duplicate
Priority: Low
Fix Version/s: None
Affects Version/s: 4.21.0, (19)
4.22.0, 4.21.1, 4.22.1, 5.0.0, 4.22.2, 4.22.3, 5.1.0, 4.22.4, 4.22.6, 5.1.1, 5.2.0, 5.3.0, 4.20.14, 5.4.0, 4.20.15, 5.3.1, Insight 8.10.13, 4.20.16, Assets 8.10.15
Component/s: Assets - Automation
Labels:
None

Symptom Severity:
Severity 3 - Minor
Bug Fix Policy:
View Atlassian Server bug fix policy

Issue Summary

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

This bug affects Jira Service Management Data Center installations with the bundled Assets/Insight since the Jira Service Management 4.20.14+.

This bug also affects the installations which do not come with the bundled Insight/Asset add-on, any Assets/Insight 8.10.13+ from the add-on marketplace listing.

Steps to Reproduce

Install Jira Service Management 4.20.14 (or any other affected version listed above) on a Windows machine.
Create an Assets/Insight schema;
On this schema configure an Assets/Insight automation with the Execute Groovy script action;

Enter the absolute Groovy script location in the File path field;
Example:

C:\Program Files\Atlassian\Aplication Data\Jira\scripts\somefile.groovy

Save.

Expected Results

Automation will successfully save without any error.

Actual Results

We see the following error on the UI:

Script file path must be absolute

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List

image-2022-12-06-13-57-51-865.png
231 kB
06/Dec/2022 4:57 PM

duplicates

JSDSERVER-12219 On windows env, Automation Rule Action "Execute Groovy script" is failing with the input validation error "Script file path must be absolute" for the file path

Gathering Impact

Form Name

Rodrigo Jose Zaparoli made changes - 07/Dec/2022 1:49 PM

Resolution		New: Duplicate [ 3 ]
Status	Original: Needs Triage [ 10030 ]	New: Closed [ 6 ]

Rodrigo Jose Zaparoli made changes - 07/Dec/2022 1:44 PM

Link

New: This issue duplicates JSDSERVER-12219 [ JSDSERVER-12219 ]

Rodrigo Jose Zaparoli made changes - 06/Dec/2022 5:40 PM

Attachment

Original: image-2022-12-06-13-57-13-236.png [ 431612 ]

Rodrigo Jose Zaparoli made changes - 06/Dec/2022 5:08 PM

Description

Original: h3. Issue Summary

In *Assets/Insight automation* the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action does not recognize *Windows* path.

(i) This bug affects Jira Service Management Data Center installations *with the bundled* Assets/Insight since the {*}Jira Service Management 4.20.14+{*}.

(i) This bug also affects the installations *which do not* come with the bundled Insight/Asset add-on, any *Assets/Insight 8.10.13+* from the [add-on marketplace listing|https://marketplace.atlassian.com/apps/1212137/insight-asset-management/version-history].
h3. Steps to Reproduce
# Install *Jira Service Management 4.20.14* (or any other affected version listed above) on a *Windows* machine.
# Create an Assets/Insight schema;
# On this schema configure an Assets/Insight automation with the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action;
# Enter the absolute Groovy script location in the File path field;
Example:
{code:java}
C:\Program Files\Atlassian\Aplication Data\Jira\scripts\somefile.groovy
{code}
# Save;

h3. Expected Results

Automation will successfully save without any error.

h3. Actual Results

We see the following error on the UI:

!image-2022-12-06-13-57-51-865.png|width=519,height=280!
{code:java}
Script file path must be absolute
{code}
h3. Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

New: h3. Issue Summary

In *Assets/Insight automation* the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action does not recognize *Windows* path.

(i) This bug affects Jira Service Management Data Center installations *with the bundled* Assets/Insight since the {*}Jira Service Management 4.20.14+{*}.

(i) This bug also affects the installations *which do not* come with the bundled Insight/Asset add-on, any *Assets/Insight 8.10.13+* from the [add-on marketplace listing|https://marketplace.atlassian.com/apps/1212137/insight-asset-management/version-history].
h3. Steps to Reproduce
# Install *Jira Service Management 4.20.14* (or any other affected version listed above) on a *Windows* machine.
# Create an Assets/Insight schema;
# On this schema configure an Assets/Insight automation with the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action;
# Enter the absolute Groovy script location in the File path field;
Example:
{code:java}
C:\Program Files\Atlassian\Aplication Data\Jira\scripts\somefile.groovy
{code}
# Save.

h3. Expected Results

Automation will successfully save without any error.

h3. Actual Results

We see the following error on the UI:

!image-2022-12-06-13-57-51-865.png|width=519,height=280!
{code:java}
Script file path must be absolute
{code}
h3. Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Rodrigo Jose Zaparoli made changes - 06/Dec/2022 5:07 PM

Description

Original: h3. Issue Summary

In *Assets/Insight automation* the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action does not recognize *Windows* path.

(i) This bug affects Jira Service Management Data Center installations *with the bundled* Assets/Insight since the {*}Jira Service Management 4.20.14+{*}.

(i) This bug also affects the installations *which do not* come with the bundled Insight/Asset add-on, any *Assets/Insight 8.10.13+* from the [add-on marketplace listing|https://marketplace.atlassian.com/apps/1212137/insight-asset-management/version-history].
h3. Steps to Reproduce
# Install *Jira Service Management 4.20.14* (or any other affected version listed above) on a *Windows* machine.
# Create an Assets/Insight schema;
# On this schema configure an Assets/Insight automation with the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action;
# Enter the absolute Groovy script location in the File path field;
Example:
{code:java}
C:\Program Files\Atlassian\Aplication Data\Jira\scripts\somefile.groovy
{code}

# Save;

h3. Expected Results

Automation will successfully save without any error.

h3. Actual Results

We see the following error on the UI:

!image-2022-12-06-13-57-51-865.png|width=519,height=280!
{code:java}
Script file path must be absolute
{code}
h3. Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

New: h3. Issue Summary

In *Assets/Insight automation* the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action does not recognize *Windows* path.

(i) This bug affects Jira Service Management Data Center installations *with the bundled* Assets/Insight since the {*}Jira Service Management 4.20.14+{*}.

(i) This bug also affects the installations *which do not* come with the bundled Insight/Asset add-on, any *Assets/Insight 8.10.13+* from the [add-on marketplace listing|https://marketplace.atlassian.com/apps/1212137/insight-asset-management/version-history].
h3. Steps to Reproduce
# Install *Jira Service Management 4.20.14* (or any other affected version listed above) on a *Windows* machine.
# Create an Assets/Insight schema;
# On this schema configure an Assets/Insight automation with the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action;
# Enter the absolute Groovy script location in the File path field;
Example:
{code:java}
C:\Program Files\Atlassian\Aplication Data\Jira\scripts\somefile.groovy
{code}
# Save;

h3. Expected Results

Automation will successfully save without any error.

h3. Actual Results

We see the following error on the UI:

!image-2022-12-06-13-57-51-865.png|width=519,height=280!
{code:java}
Script file path must be absolute
{code}
h3. Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Rodrigo Jose Zaparoli made changes - 06/Dec/2022 5:07 PM

Description

Original: h3. Issue Summary

In *Assets/Insight automation* the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action does not recognize *Windows* path.

(i) This bug affects Jira Service Management Data Center installations *with the bundled* Assets/Insight since the {*}Jira Service Management 4.20.14+{*}.

(i) This bug also affects the installations *which do not* come with the bundled Insight/Asset add-on, any *Assets/Insight 8.10.13+* from the [add-on marketplace listing|https://marketplace.atlassian.com/apps/1212137/insight-asset-management/version-history].
h3. Steps to Reproduce
# Install *Jira Service Management 4.20.14* (or any other affected version listed above) on a *Windows* machine.
# Create an Assets/Insight schema;
# On this schema configure an Assets/Insight automation with the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action;
# Enter the absolute Groovy script location in the File path field;
Example:
{code}
C:\Program Files\Atlassian\Aplication Data\Jira\scripts\somefile.groovy
{code}
# Hit add;

h3. Expected Results

Automation will successfully save without any error.

h3. Actual Results

We see the following error on the UI:

!image-2022-12-06-13-57-51-865.png|width=519,height=280!
{code:java}
Script file path must be absolute
{code}
h3. Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

New: h3. Issue Summary

In *Assets/Insight automation* the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action does not recognize *Windows* path.

(i) This bug affects Jira Service Management Data Center installations *with the bundled* Assets/Insight since the {*}Jira Service Management 4.20.14+{*}.

(i) This bug also affects the installations *which do not* come with the bundled Insight/Asset add-on, any *Assets/Insight 8.10.13+* from the [add-on marketplace listing|https://marketplace.atlassian.com/apps/1212137/insight-asset-management/version-history].
h3. Steps to Reproduce
# Install *Jira Service Management 4.20.14* (or any other affected version listed above) on a *Windows* machine.
# Create an Assets/Insight schema;
# On this schema configure an Assets/Insight automation with the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action;
# Enter the absolute Groovy script location in the File path field;
Example:
{code:java}
C:\Program Files\Atlassian\Aplication Data\Jira\scripts\somefile.groovy
{code}

# Save;

h3. Expected Results

Automation will successfully save without any error.

h3. Actual Results

We see the following error on the UI:

!image-2022-12-06-13-57-51-865.png|width=519,height=280!
{code:java}
Script file path must be absolute
{code}
h3. Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Rodrigo Jose Zaparoli made changes - 06/Dec/2022 5:07 PM

Description

Original: h3. Issue Summary

In *Assets/Insight automation* the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action does not recognize *Windows* path.

(i) This bug affects Jira Service Management Data Center installations *with the bundled* Assets/Insight since the {*}Jira Service Management 4.20.14+{*}.

(i) This bug also affects the installations *which do not* come with the bundled Insight/Asset add-on, any *Assets/Insight 8.10.13+* from the [add-on marketplace listing|https://marketplace.atlassian.com/apps/1212137/insight-asset-management/version-history].
h3. Steps to Reproduce
# Install *Jira Service Management 4.20.14* (or any other affected version listed above) on a *Windows* machine.
# Create an Assets/Insight schema;
# On this schema configure an Assets/Insight automation with the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action;
# Enter the absolute Groovy script location in the File path field;
# Hit add;

h3. Expected Results

Automation will successfully save without any error.

h3. Actual Results

We see the following error on the UI:

!image-2022-12-06-13-57-51-865.png|width=519,height=280!
{code:java}
Script file path must be absolute
{code}
h3. Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

New: h3. Issue Summary

In *Assets/Insight automation* the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action does not recognize *Windows* path.

(i) This bug affects Jira Service Management Data Center installations *with the bundled* Assets/Insight since the {*}Jira Service Management 4.20.14+{*}.

(i) This bug also affects the installations *which do not* come with the bundled Insight/Asset add-on, any *Assets/Insight 8.10.13+* from the [add-on marketplace listing|https://marketplace.atlassian.com/apps/1212137/insight-asset-management/version-history].
h3. Steps to Reproduce
# Install *Jira Service Management 4.20.14* (or any other affected version listed above) on a *Windows* machine.
# Create an Assets/Insight schema;
# On this schema configure an Assets/Insight automation with the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action;
# Enter the absolute Groovy script location in the File path field;
Example:
{code}
C:\Program Files\Atlassian\Aplication Data\Jira\scripts\somefile.groovy
{code}
# Hit add;

h3. Expected Results

Automation will successfully save without any error.

h3. Actual Results

We see the following error on the UI:

!image-2022-12-06-13-57-51-865.png|width=519,height=280!
{code:java}
Script file path must be absolute
{code}
h3. Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Rodrigo Jose Zaparoli made changes - 06/Dec/2022 5:04 PM

Description

Original: h3. Issue Summary

In *Assets/Insight automation* the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action does not recognize Windows path.

(i) This bug affects Jira Service Management Data Center installations *with the bundled* Assets/Insight since the {*}Jira Service Management 4.20.14+{*}.

(i) This bug also affects the installations *which do not* come with the bundled Insight/Asset add-on, any *Assets/Insight 8.10.13+* from the [add-on marketplace listing|https://marketplace.atlassian.com/apps/1212137/insight-asset-management/version-history].
h3. Steps to Reproduce
# Install *Jira Service Management 4.20.14* (or any other affected version listed above) on a Windows machine.
# Create an Assets/Insight schema;
# On this schema configure an Assets/Insight automation with the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action;
# Enter the absolute Groovy script location in the File path field;
# Hit add;

h3. Expected Results

Automation will successfully save without any error.

h3. Actual Results

We see the following error on the UI:

!image-2022-12-06-13-57-51-865.png|width=519,height=280!
{code}
Script file path must be absolute
{code}

h3. Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

New: h3. Issue Summary

In *Assets/Insight automation* the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action does not recognize *Windows* path.

(i) This bug affects Jira Service Management Data Center installations *with the bundled* Assets/Insight since the {*}Jira Service Management 4.20.14+{*}.

(i) This bug also affects the installations *which do not* come with the bundled Insight/Asset add-on, any *Assets/Insight 8.10.13+* from the [add-on marketplace listing|https://marketplace.atlassian.com/apps/1212137/insight-asset-management/version-history].
h3. Steps to Reproduce
# Install *Jira Service Management 4.20.14* (or any other affected version listed above) on a *Windows* machine.
# Create an Assets/Insight schema;
# On this schema configure an Assets/Insight automation with the [Execute Groovy script|https://confluence.atlassian.com/servicemanagementserver0421/configuring-insight-automation-rules-1115654234.html#:~:text=every%20THEN%20box.-,Available%20actions,-Here%27s%20a%20list] action;
# Enter the absolute Groovy script location in the File path field;
# Hit add;

h3. Expected Results

Automation will successfully save without any error.

h3. Actual Results

We see the following error on the UI:

!image-2022-12-06-13-57-51-865.png|width=519,height=280!
{code:java}
Script file path must be absolute
{code}
h3. Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Rodrigo Jose Zaparoli created issue - 06/Dec/2022 5:03 PM

Assignee:: Unassigned

Reporter:: Rodrigo Jose Zaparoli

Affected customers:: 2 This affects my team

Watchers:: 4 Start watching this issue

Created:: 06/Dec/2022 5:03 PM

Updated:: 07/Dec/2022 1:49 PM

Resolved:: 07/Dec/2022 1:49 PM

Details

Description

Issue Summary

Steps to Reproduce

Expected Results

Actual Results

Workaround

Attachments

Attachments

Issue Links

Forms

Activity

People

Dates

Backbone Issue Sync