• 120
    • 10
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      At the moment, mention only works in System field (Comment and Description). It would be great to make it works on custom text field as well.

          Form Name

            [JRASERVER-32563] Mentions should work with text custom fields

            y.poulin added a comment -

            The more i use Jira the more i miss service now. This should be available to use for custom fields, i created many fields using the Paragraph (Support rich text)

             

            and what i get is:

             

             

            Please fix this asap, we are in 2024 cheetos.....

            y.poulin added a comment - The more i use Jira the more i miss service now. This should be available to use for custom fields, i created many fields using the Paragraph (Support rich text)   and what i get is:     Please fix this asap, we are in 2024 cheetos.....

            Adan Warren added a comment - - edited

            I made an automation for this. It splits all text by non-alphanumeric (while keeping those characters in their splits), so you're left with just @email which is then converted to "[~email@example.com]". It could certainly be improved for speed, but it works for the most part.

            {{#issue.Project Progress Update.split("((?<=[^A-Za-z0-9@])|(?=[^A-Za-z0-9@]))")}}{{#if(not(startsWith("@")))}}{{.}}{{/}}{{#if(startsWith("@"))}}[~{{substring(1)}}@example.com]{{/}}{{/}}
            

            This sets up a list of emails for newly mentioned people to be notified by another automation of your design:

            {{#issue.Project Progress Update.split("((?<=[^A-Za-z0-9@])|(?=[^A-Za-z0-9@]))")}}{{#if(startsWith("@"))}}{{substring(1)}}@example.com, {{/}}{{/}}
            

            Adan Warren added a comment - - edited I made an automation for this. It splits all text by non-alphanumeric (while keeping those characters in their splits), so you're left with just @email which is then converted to "[~email@example.com]". It could certainly be improved for speed, but it works for the most part. {{#issue.Project Progress Update.split( "((?<=[^A-Za-z0-9@])|(?=[^A-Za-z0-9@]))" )}}{{# if (not(startsWith( "@" )))}}{{.}}{{/}}{{# if (startsWith( "@" ))}}[~{{substring(1)}}@example.com]{{/}}{{/}} This sets up a list of emails for newly mentioned people to be notified by another automation of your design: {{#issue.Project Progress Update.split( "((?<=[^A-Za-z0-9@])|(?=[^A-Za-z0-9@]))" )}}{{# if (startsWith( "@" ))}}{{substring(1)}}@example.com, {{/}}{{/}}

            Nikolaj Skov added a comment - - edited

            I've experiences that using "[ ~ accountID]" (without the spaces) works as an alternative. This doesn't prompt the autocomplete, so it requires that you know the id of the user you want to tag. This works both in visual and text views of the field. 

            This is an odd workaround and feels mostly like a bug. 

             

            Nikolaj Skov added a comment - - edited I've experiences that using "[ ~ accountID]" (without the spaces) works as an alternative. This doesn't prompt the autocomplete, so it requires that you know the id of the user you want to tag. This works both in visual and text views of the field.  This is an odd workaround and feels mostly like a bug.   

            Kaja Bryl added a comment -

            Sadly it does not.

            Kaja Bryl added a comment - Sadly it does not.

            Matt Doar added a comment -

            Does this work if you change the field renderer to the Wiki renderer?

            Matt Doar added a comment - Does this work if you change the field renderer to the Wiki renderer?

            +100 how is this not a thing yet? It feels like a bug. 

            Jamie Gerace added a comment - +100 how is this not a thing yet? It feels like a bug. 

            +1

            Erik de Bruin added a comment - +1

            We use Jira Automation (Cloud version) as a workaround to copy the @mention to comment field, when the field is updated with @mention.  This is dumb but works for us.

            Using "Advanced compare condition" check if field contains:

            [~accountid:.+]

            Then use "Comment on Issue" action to include content of that field in comment section.

             

             

             

             

            Vincent Cheung added a comment - We use Jira Automation (Cloud version) as a workaround to copy the @mention to comment field, when the field is updated with @mention.  This is dumb but works for us. Using "Advanced compare condition" check if field contains: [~accountid:.+] Then use "Comment on Issue" action to include content of that field in comment section.        

            Is there any kind of workaround for this?

            Barney Dalton added a comment - Is there any kind of workaround for this?

            +1

              Unassigned Unassigned
              vkharisma vkharisma
              Votes:
              468 Vote for this issue
              Watchers:
              230 Start watching this issue

                Created:
                Updated: