nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Scriptrunner Escalation Service not adding comment if Action is None

Andrew Culver

I have created 2 Escalation Services which have Action set to perform a transition. I'm now trying to create a 3rd Escalation Service which has Action set to none. When I run it, the comment is not being added, as it is with the other 2 Escalation Services.

It seems that not having an Action means no comment is added. Maybe because there is no screen?

Here's one of the Escalation services which have an action. The one I'm trying to add has a different JQL (still matches some issues), no Action, different comment, but still uses issueInputParameters.setComment.

Description: Transition inactive issues in Waiting For Reporter status to Inactive - Pending Closure status
Interval: 60
JQL: status = "Waiting For Reporter" AND updated <= -1w
Action: 301 Reporter Inactive
Run as: jirabot
Additional Code:
def comment = """
This issue has not been updated for 7 days.

If you have an update, please update the issue. If you need more time to gather information please freeze the issue. If you have no other questions, please close this issue.

If no update is received in the next 7 days, this issue will be automatically closed.

Thank you,
Jira Automation Bot
WTS
"""

issueInputParameters.setComment(comment)

Accepted answers

All comments

Joshua Yamdogo @ Adaptavist

Which version of SR is this? Another customer has brought up this problem today, but I cannot reproduce it. I don't think you need to define an action to add a comment, as I have successfully added a comment without an action:

Screen Shot 2018-03-12 at 8.36.26 AM.png

Screen Shot 2018-03-12 at 8.35.22 AM.png

Thanks,

Josh

Joshua Yamdogo @ Adaptavist

Our docs state:

Action
What action do you want to run on the issue? This is optional, you can use Additional Issue Actions instead or as well as

https://scriptrunner.adaptavist.com/latest/jira/escalation-service.html

Andrew Culver

Jira 7.7.1 and Scriptrunner 5.3.5. I see 5.3.7 is available. I'll update now and try again.

Andrew Culver

Joshua Yamdogo @ Adaptavist I saw that as well.

I just tried again with 5.3.7. In the add escalation service screen, I click Run now, and it shows 63 issues returned and says they were updated (as yours did), but none of the issues have any comment added. I can also click Run now again, and it still says 63 issues returned -- but there should be 0 if a comment was just added, since the JQL query is looking for issues update <= -2w.

Here's a screenshot:

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

scriptrunner

jira