update an issue field on event "issue updated"

[RPO]

Hello,

I want to update a Field of an issue every time this issue is updated. To do that i am using a listener on the event "issue updated" with a little script:

def summary = event.issue.getSummary()
def type = event.issue.issueType.getName()
if (type == 'Epic') {
    event.issue.update {
      setEpicName(summary)
  }
}

However i imagine this it would create an infinite trigger of the "issue updated" event, as i am updating the issue with my script either.

Is this the case? or scriptrunner's scripts do not trigger events events like "issue updated"?

setEpicName

[RPO · Accepted solution]

I run some tests and the answer is yes.

The command

event.issue.update {... }

will  generate a new "issue updated" trigger.
if not used correctly the issue will be updated recursively many times.

I have solved the problem with this code:

import com.atlassian.jira.event.type.EventDispatchOption
import com.atlassian.jira.issue.Issue

Issue issue = event.getIssue()
def type = issue.issueType.getName()
def summary = issue.getSummary()
def epicName = issue.getEpicName()
if (type == 'Epic') {
    if (summary != epicName) {
        issue.update {
            setEpicName(summary)
            setEventDispatchOption(EventDispatchOption.DO_NOT_DISPATCH)
            setSendEmail(false)
        }
    }
}

[Leonel Goitia]

Hi, agree with @Marc - Devoteam

you can use this trigger

[RPO]

I am exploring possibilities.  :)

[Uladzislau Samuseu]

Hi @RPO 

May be you have to add a check at the beginning like "if summary is not updated".

[RPO]

true, i will.

but the main question is if the script triggers automatically an event when i update an issue, or not

[Marc - Devoteam]

Hi @RPO 

Welcome to the community.

Why don't you use an automation rule for this?

[RPO]

I am exploring possibilities.  What is the benefit of automation other than simplicity of implementation?

anyway, the main question is if the script triggers automatically an event when i update an issue, or not