Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-79268

Ability to @mention a user or group in a comment via Automation

    • 7
    • 13
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      Sometimes we need to mention a group e.g.: @admins in the comments. Considering this, we should be able to mention a group. For example: 

      [~admins]
      [~users-group]
      

      Workaround

      The previous workaround is not available anymore.

      As a workaround, I recommend replacing the "Add comment" action with a "Send web request" action for greater flexibility. This approach allows you to manually craft the storage format and utilize it via this endpoint:

      This method also enables you to specify the correct page by resolving the `page.id` within the request body.

            [CONFCLOUD-79268] Ability to @mention a user or group in a comment via Automation

            Pinned comments

            Pinned by Trevor Angle

            Trevor Angle added a comment - - edited

            Hi everyone,

            This is Trevor from the Confluence team. It is now possible to mention a user through Confluence automation. The syntax is the same as Jira automation, and it looks like this:

            accountId:<the account ID>

            For example, accountId:12345. You can also combine this with smart values, eg {{page.author.accountId}}.

            This syntax works in the 'Add comment' action and the 'Publish new page' action (if you include content in the page body).

            Note that we have not yet added support for mentioning groups through Confluence automation. Please continue to vote and comment on this ticket with your needs and use-cases for mentioning groups with automation.

            Best,

            Trevor Angle

            Trevor Angle added a comment - - edited Hi everyone, This is Trevor from the Confluence team. It is now possible to mention a user through Confluence automation. The syntax is the same as Jira automation, and it looks like this: accountId:<the account ID> For example,  accountId:12345 . You can also combine this with smart values, eg {{ page.author.accountId }} . This syntax works in the 'Add comment' action and the 'Publish new page' action (if you include content in the page body). Note that we have not yet added support for mentioning groups through Confluence automation. Please continue to vote and comment on this ticket with your needs and use-cases for mentioning groups with automation. Best, Trevor Angle

            All comments

            Pinned by Trevor Angle

            Trevor Angle added a comment - - edited

            Hi everyone,

            This is Trevor from the Confluence team. It is now possible to mention a user through Confluence automation. The syntax is the same as Jira automation, and it looks like this:

            accountId:<the account ID>

            For example, accountId:12345. You can also combine this with smart values, eg {{page.author.accountId}}.

            This syntax works in the 'Add comment' action and the 'Publish new page' action (if you include content in the page body).

            Note that we have not yet added support for mentioning groups through Confluence automation. Please continue to vote and comment on this ticket with your needs and use-cases for mentioning groups with automation.

            Best,

            Trevor Angle

            Trevor Angle added a comment - - edited Hi everyone, This is Trevor from the Confluence team. It is now possible to mention a user through Confluence automation. The syntax is the same as Jira automation, and it looks like this: accountId:<the account ID> For example,  accountId:12345 . You can also combine this with smart values, eg {{ page.author.accountId }} . This syntax works in the 'Add comment' action and the 'Publish new page' action (if you include content in the page body). Note that we have not yet added support for mentioning groups through Confluence automation. Please continue to vote and comment on this ticket with your needs and use-cases for mentioning groups with automation. Best, Trevor Angle

            Avinoam added a comment -

            We're actively working on adding user @mention support and will also evaluate potentially adding support for group @mentions a bit later.

            Avinoam added a comment - We're actively working on adding user @mention support and will also evaluate potentially adding support for group @mentions a bit later.

            This impacts automation I created within Confluence. The workaround does work for me, but isn't ideal. Being able to explicitly specify users (by name), via the proper component, would be a much more straight forward process.

            Gary Spross added a comment - This impacts automation I created within Confluence. The workaround does work for me, but isn't ideal. Being able to explicitly specify users (by name), via the proper component, would be a much more straight forward process.

            https://jira.atlassian.com/browse/JRACLOUD-80134

            Can see that the link above is also gathering interest

            Natalie Waters added a comment - https://jira.atlassian.com/browse/JRACLOUD-80134 Can see that the link above is also gathering interest

            We are now hitting instance email limits because Jira Automation does not have this feature. We need to issue group notifications when certain issues reach a specific status. The addresses are set in a user group. But the only way to address user groups via automation is via email (our company does not use internal chat like slack or teams). This means that there is no scalability. We are now hitting the cap on the outgoing emails per 24h

            Diogo Teles added a comment - We are now hitting instance email limits because Jira Automation does not have this feature. We need to issue group notifications when certain issues reach a specific status. The addresses are set in a user group. But the only way to address user groups via automation is via email (our company does not use internal chat like slack or teams). This means that there is no scalability. We are now hitting the cap on the outgoing emails per 24h

            How is this not already something that exists?

            Having to type IDs doesn't tell us who's there and if we hire some one else we have to edit all of our automation. 

            Andrew Herrera added a comment - How is this not already something that exists? Having to type IDs doesn't tell us who's there and if we hire some one else we have to edit all of our automation. 

            The workaround unfortunately is temporal and when the user changes then every time the rule requires to be edited. 

            Deleted Account (Inactive) added a comment - The workaround unfortunately is temporal and when the user changes then every time the rule requires to be edited. 

              azelenko Avinoam
              cfontana@atlassian.com Cristiano
              Votes:
              103 Vote for this issue
              Watchers:
              58 Start watching this issue

                Created:
                Updated: