Versions Compared

Key

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

Users

When using the "user parameter " parameter in a JSON trigger, It is only possible to include the userIDand in some cases a user type workflow parameter.

(info) A JSON trigger action does not accept the Confluence userName.

In the example below, the assign trigger action uses the Confluence userID.

Code Block
"triggers:"
[
    {"event": "on-change-state",
    "conditions":
    [
        {"state": "Review"}
    ],
    "actions":
    [
        {"action": "assign",
            "approval": "Teamreview",
            "user": "5d52a37ef0f22a0da2d6f070"}
    ]}
]

...

In the example below, the approve trigger action specifies the approver using a Confluence userID.

Code Block
"triggers":
[
    {"event": "on-change-state",
    "conditions":
    [
        {"state": "Review"}
    ],
    "actions":
    [
        {"action": "approve",
            "approval": "Teamreview",
            "user": "5d52a37ef0f22a0da2d6f070"}
    ]}
]

The "user" parameter is used in the following JSON trigger actions:

"approve"

"reject"

"assign"

"unassign"

The userId can also be added to the recipient parameter in the "send-email" trigger email trigger action.

Groups

When using the "group parameter " parameter in a JSON trigger, you can include either the groupName and/or the groupIDand in some cases a group type workflow parameter.

In the example below, the "send-email" email trigger action uses the Confluence group name  qa_reviewteam for the recipients of the custom email.

...

For trigger actions, the "group" parameter is only currently used in the

...

(info) For triggers, a user or group type workflow parameter is only currently valid for use in  the " the send-email "trigger action as  as a value for "recipients".

Code Block
"triggers":
[
    {"event": "on-change-state",
    "conditions":
    [
        {"state": "Approved"}
    ],
    "actions":
    [
        {"action": "send-email",
            "recipients":
            [
                "@creator",
                "@my_project_team@",
				"@my_QA_leader@"
			],
            "notification": {"subject": "${content.title} is in the Approved published state",
                "title": "${content.title} is in the Approved published state",
                "body": "Hello, ${content.link} in the ${content.space} space is in the Approved published state"}}
	]}
]

...