Versions Compared

Old Version 1

changes.mady.by.user Mike Harrison

Saved on

compared with

New Version Current

changes.mady.by.user Andy Brook [Plugin People]

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Sometimes you will want to treat a particular issue event as if it were another. Normally this will be only when certain conditions are met.

Step-by-step guide

  1. Go to JEMH >

    Event ListenerCreate a new configuration mapping or edit an existing one

    Notifications

  2. Find/create a notification mapping

  3. In the

    "

    Event Selector and Filter script

    "

    section, enter your script, using Velocity scripting language. Refer to the following page for more information on creating the script: https://thepluginpeople.atlassian.net/wiki/x/VgAwB

 The following example script will treat all events with comments as Issue Commented events, except when the original event has the event type ID 10000:

Info
title

Example script

#if($comment

&&

$issueEvent.getEventTypeId()

!=

10000)

$result.setTargetEventId(6)

$result.setEventBroadcastMethod('useDerivedEventInstead')

$result.setReason('event

with

comment

should

be

comment

event

type')

#end

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@957
sortmodified
showSpacefalse

...

reversetrue
typepage
cqllabel in ( "event-type" , "event" , "event-listener" , "notifications" ) and type = "page" and space = "KB"
labelsevent-listener event notifications event-type


Page Properties
hiddentrue


Related issues