Details
-
Type:
Bug
-
Status: Done
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 5.6.14.1-p5, 5.9.0, 6.3.0, 6.11.0
-
Fix Version/s: None
-
Component/s: REST EndPoint
-
Labels:
-
Critical Points:3.5
Description
For Script Runner version 5.6.14.1-p5
Steps to Reproduce
- Create a REST Endpoint using a File and Save it.
- Once the REST Endpoint is created, open it for Editing once again.
- Next go to the File tab once again.
- Now open a new tab on the web browser or just click on another tab in the web browser if it is already open.
- Once in the new tab, go back to the REST Endpoint tab once again.
Current Behaviour
The File path that was previously configured goes blank
Expected Behaviour
When returning to the tab, the file path is still expected to be available.
For ScriptRunner version 5.9.0-p5
Steps to Reproduce
- Create a REST Endpoint using a File and Save it.
- Once the REST Endpoint is created, open it for Editing once again.
Current Behaviour
- The field tab is not editable.
- When you are in the Script tab, you will need to click the backspace key once in the Script Field for the File tab to be enabled.
- Once the File tab is enabled, click on the File tab, you will notice that the File previously configured is blank
Expected Behaviour
- The File tab is also expected to be enabled
- Also, when the file tab is clicked, the File path is expected to be available.
Workaround
- Edit your REST Endpoint
- Go to the Script Tab.
- Click the backspace key once in the Script Field for the File tab to be enabled.
Additional Info
- Below are 2 Test Videos for both ScriptRunner versions
Attachments
Issue Links
- is related to
-
SRPLAT-1271 Existing REST Endpoints using an inline script cannot switch to File tab
-
- Done
-
- relates to
-
SRJIRA-4813 Using External Script located inside a directory in REST Endpoint causes HTTP 500 error and Found by class scanning and can't be edited here
-
- Done
-