Scriptrunner: Add a Condition to a Web Section Limiting Issue Type

[Michael Thompson]

Having some trouble with Script Fragments in Jira Software 8.1.0. and Adaptavist ScriptRunner 5.5.6.1-jira8.

GOAL

One of my projects contains a unique Issue Type called AWS Migrations. We create a parent issue and six sub-tasks underneath it for each software environment (QA, Pre-Prod, Practice, Production, and Demo).

I want to replace the Clone button with multiple scripts to Clone to P_PRE, Clone to P_PS, Clone to P_PRD, and Clone to P_DEM. This will allow me to create a custom clone script that also edits certain values in the master ticket that are important for each environment.

PROBLEM

My first script fragment should hide the Clone option from the More dropdown, but only if the Issue Type is AWS Migrations. I added the following condition and it works fine.

! (issue.issueType.name == "AWS Migration")

My next script fragment is to add a new option Clone to P_PRE to the More dropdown. Since this should only be available if Issue Type is AWS Migrations, I figured this should work.

issue.issueType.name == "AWS Migration"

Instead, I get the following checking error:

[Static type checking] - The variable [issue] is undeclared.
@ line 1, column 1.

QUESTION

Why is this happening? What is the correct syntax for the condition?

[Leonard Chew · Accepted solution]

This is a good question, and I don't know the answer, but my best guess would be that your environment is sometimes returning milliseconds instead of days.

Try an explicit cast to milliseconds and then recalculate the day value, e.g.

def dateValueInMs = dateValue.getTime()

def dateValue2InMs = dateValue2.getTime()

return (dateValueInMs-dateValue2InMs)/1000/60/60/24

[Dianne M Fry-Bolton]

Thank you!  I couldn't get the .getTime() to work for me, but I was able to adjust my calculation accounting for the milliseconds.  Just waiting for it to break again.

I appreciate your help!