• 136
    • 14
    • Hide
      Atlassian Update – 28 February 2018

      Hi everyone,

      Thanks for your interest in this issue.
      This request is considered a potential addition to our longer-term roadmap.

      We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

      For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including:

        • Performance and stability improvements
        • Archiving projects for improved performance
        • Optimising the use of custom fields
        • Improving performance of boards
        • Improving Jira notifications
        • Allowing users to edit shared filters and dashboards
        • Mobile app for Jira Server

      You can learn more about our approach to highly voted server suggestions here.

      To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 28 February 2018 Hi everyone, Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Archiving projects for improved performance Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server You can learn more about our approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Jira Server Product Management
    • 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.

      Often times, I'd like to mention an entire group in JIRA rather than individual users.

      Obviously this has the potential to be abused in large instances such as this, but the ability to disable combined with a list of groups that can be mentioned could mitigate these concerns.

      An additional safe-guard may be to limit who can mention certain groups.

            [JRASERVER-28225] Mentions of groups

            +1

            Eetu Heino added a comment -

            +1

            Eetu Heino added a comment - +1

            +1

            +1

            Anthony Romm added a comment - +1

            Waiting for any updates!

            Aleksandra Leesment added a comment - Waiting for any updates!

            TH.Kang added a comment -

            +1

            TH.Kang added a comment - +1

            ckent added a comment - - edited

            Hello @Daniel Cosmus, thank you for the creation of your Jira Plug-in app: User Mention Groups for the Richtext Editor, however, the core concern and reason this particular tickets exists (JRASERVER-28225) is because this behavior and functionality should be inherit behavior. It should not require additional costs or extensions.

            This type of functionality is critical to maintaining team communication and coordination and has been an industry standard for these types of Tools / Applications for decades (Microsoft Outlook, Google Gmail), also many products that are direct competitors to Jira, like Monday, Asana, Aha etc. all have this feature by default as well.

            In my opinion, this is a major mis-step my Atlassian for multiple reasons. That said, the big one for me is that this has been a long standing ticket created back in  10/May/2012..., being over a decade old, it clearly indicates that Jira / Atlassian do not care about or prioritize User Feedback and Requests.

             

            That is the problem!

            ckent added a comment - - edited Hello @Daniel Cosmus, thank you for the creation of your Jira Plug-in app: User Mention Groups for the Richtext Editor , however, the core concern and reason this particular tickets exists ( JRASERVER-28225 ) is because this behavior and functionality should be inherit behavior. It should not require additional costs or extensions. This type of functionality is critical to maintaining team communication and coordination and has been an industry standard for these types of Tools / Applications for decades (Microsoft Outlook, Google Gmail), also many products that are direct competitors to Jira, like Monday, Asana, Aha etc. all have this feature by default as well. In my opinion, this is a major mis-step my Atlassian for multiple reasons. That said, the big one for me is that this has been a long standing ticket created back in  10/May/2012 ..., being over a decade old, it clearly indicates that Jira / Atlassian do not care about or prioritize User Feedback and Requests.   That is the problem!

            +1

            Yichi Zhang added a comment - +1

            Hello,

            i created an plugin where you are able to mention different groups.

            Every user can create there own (just the creator of the group can use this group) or global (every user can use the group) mention groups. At the moment the groups are displayed in the toolbar in the richttext editor and can be selected, but a new feature will allow to use the mention search to select the groups.
            https://dagrato.atlassian.net/wiki/spaces/UMGFTRE/pages/307298323/FAQ

            Marketplace:

            https://marketplace.atlassian.com/apps/1224368/user-mention-groups-for-the-richtext-editor?hosting=datacenter&tab=overview

             

            Daniel Cosmus added a comment - Hello, i created an plugin where you are able to mention different groups. Every user can create there own (just the creator of the group can use this group) or global (every user can use the group) mention groups. At the moment the groups are displayed in the toolbar in the richttext editor and can be selected, but a new feature will allow to use the mention search to select the groups. https://dagrato.atlassian.net/wiki/spaces/UMGFTRE/pages/307298323/FAQ Marketplace: https://marketplace.atlassian.com/apps/1224368/user-mention-groups-for-the-richtext-editor?hosting=datacenter&tab=overview  

            +1  

            Thomas Peyerl added a comment - +1  

            Up

            reuben.jusay added a comment - Up

            mb added a comment -

            bump

            mb added a comment - bump

            ckent added a comment -

            +1

            This behavior should be default functionality of the Site and your paying Customers should not be reliant on 3rd Party Plug-in's / Addons to facilitate this behavior.

            Jira already inherently allows for User mention (@someone) Comments and provides User Management to create Groups.

            ckent added a comment - +1 This behavior should be default functionality of the Site and your paying Customers should not be reliant on 3rd Party Plug-in's / Addons to facilitate this behavior. Jira already inherently allows for User mention (@someone) Comments and provides User Management to create Groups.

            (The voting is open, it's possible to actually vote rather than comment with "+1").

            Piotr Janik added a comment - (The voting is open, it's possible to actually vote rather than comment with "+1").

            g5admins added a comment -

            +1

            g5admins added a comment - +1

            +1

            Anilkumar B added a comment - +1

            +1

            Ralf Fehling added a comment - +1

            PEGE added a comment -

            +1

            PEGE added a comment - +1

            +1

            Ali Gungormez added a comment - - edited

            +1

             

            is a must feature

            Ali Gungormez added a comment - - edited +1   is a must feature

            NazarS added a comment -

            +1

            NazarS added a comment - +1

            +1

            +1

            Alican Torun added a comment - +1

            Ivan X added a comment -

            +1

            Ivan X added a comment - +1

            +1

            would be super useful.. currently having to create fake alias users with distribution lists as emails. not very scalable

            Chris Aldridge added a comment - would be super useful.. currently having to create fake alias users with distribution lists as emails. not very scalable

            Lisa Thessen added a comment - - edited

            Hi Tom, my large firm is on the cloud version and in the new Jira Labs version, I am able to do it in the "Jira labs" view when I have it turned on in my personal settings.  I am not able to do it in the old version they are retiring March 31.  To set it up, in the "team" menu, I created my teams.  Once set-up, I am now able to use the @ (Team Name) to tag them all in comments.    Not sure if this new or not, but I can do it in the Jira Labs view only....    Are you trying to add it somewhere other than comments?  

            Lisa Thessen added a comment - - edited Hi Tom, my large firm is on the cloud version and in the new Jira Labs version, I am able to do it in the "Jira labs" view when I have it turned on in my personal settings.  I am not able to do it in the old version they are retiring March 31.  To set it up, in the "team" menu, I created my teams.  Once set-up, I am now able to use the @ (Team Name) to tag them all in comments.    Not sure if this new or not, but I can do it in the Jira Labs view only....    Are you trying to add it somewhere other than comments?  

            Tom Rufo added a comment -

            Please add this feature! I often want to tag teams of individuals, listing out 10 names individually is a huge time drain!

            Tom Rufo added a comment - Please add this feature! I often want to tag teams of individuals, listing out 10 names individually is a huge time drain!

            +1

            Ryan Nichols added a comment - +1

            Our users would like to have it as well. 

            Yurii ZHATKIN added a comment - Our users would like to have it as well. 

            +6000

            Azfar Masut added a comment - +6000

            We absolutely need this . Business users and customers are asking for this. Helps immensely with communication. Let's make this happen !!

            Arvind Rajaram added a comment - We absolutely need this . Business users and customers are asking for this. Helps immensely with communication. Let's make this happen !!

            Lucky 122... let's make this happen

            Michelle Rohan added a comment - Lucky 122... let's make this happen

            Request 121 is the one that will push it over the edge I am sure

            kevin_macharg added a comment - Request 121 is the one that will push it over the edge I am sure

            This was created more than 8 years ago and no resolution yet...

            Ryan Ballas added a comment - This was created more than 8 years ago and no resolution yet...

            LETS GO!

             

            They are probably delaying because they want you to create fake users that you pay monthly for

            Anthony Calce added a comment - LETS GO!   They are probably delaying because they want you to create fake users that you pay monthly for

            Yet another user waiting for this feature to be baked into the product.  Sad to see it is almost on its 8th anniversary.

            Dean Barrett added a comment - Yet another user waiting for this feature to be baked into the product.  Sad to see it is almost on its 8th anniversary.

            Thank you for outlining the process. I was able to set this up with some help from my tech ops folks. 

            Janene Pappas added a comment - Thank you for outlining the process. I was able to set this up with some help from my tech ops folks. 

            @Sean.M, Brilliant solution to a problem that shouldn't exist. Thank you.

            Jim Constant added a comment - @Sean.M, Brilliant solution to a problem that shouldn't exist. Thank you.

            Sean M added a comment - - edited

            @janene.pappas

            Let's say we have a Jira Project called 'Facilities Management' and you, Ic43 and Mickey and I all want to be notified when someone mentions @facilities. I would

            • go to 'User management' in Jira
            • create a new user called 'Facilities'
            • give it the email address 'facilities_managers@example.com.'
            • make sure the 'Facilities' user has browse access to the issues where we want to use the @mention
            • the 'Facilities' user should not be a member of jira-users, or any other group Jira uses to count licenses

            That should be it from the Jira set up. The rest of it is probably for your tech ops people. In this case, I would ask them to create a mailing list called 'facilities_managers@example.com' which has you, Ic43, Mickey and I as members.

            In theory, with all of that in place, you should be able to mention @facilities and the four of us will get an email. That's assuming, of course, that Jira is otherwise configured to send email notifications and your mail server works in a typical way. There are a lot of things that might prevent it from working that aren't related to Jira, which is why I'm hopeful Atlassian will render this workaround obsolete in the future.

            Sean M added a comment - - edited @janene.pappas Let's say we have a Jira Project called 'Facilities Management' and you, Ic43 and Mickey and I all want to be notified when someone mentions @facilities. I would go to 'User management' in Jira create a new user called 'Facilities' give it the email address 'facilities_managers@example.com.' make sure the 'Facilities' user has browse access to the issues where we want to use the @mention the 'Facilities' user should not be a member of jira-users, or any other group Jira uses to count licenses That should be it from the Jira set up. The rest of it is probably for your tech ops people. In this case, I would ask them to create a mailing list called 'facilities_managers@example.com' which has you, Ic43, Mickey and I as members. In theory, with all of that in place, you should be able to mention @facilities and the four of us will get an email. That's assuming, of course, that Jira is otherwise configured to send email notifications and your mail server works in a typical way. There are a lot of things that might prevent it from working that aren't related to Jira, which is why I'm hopeful Atlassian will render this workaround obsolete in the future.

            @seanm3 How did you do this? I've not been able to create a user from a mailing list, the confirmation email never arrives and my tech ops folks tell me it's not being filtered out. 

            Janene Pappas added a comment - @seanm3 How did you do this? I've not been able to create a user from a mailing list, the confirmation email never arrives and my tech ops folks tell me it's not being filtered out. 

            Any update on this?

            Mickey Somra added a comment - Any update on this?

            Sean M added a comment - - edited

            I've been creating mailing lists on our mail server for the employees in a group, then creating new unlicensed Jira users with the list's email address. I can mention that user and a notification is sent to the mailing list. A license is not needed since that user will never actually view the ticket – or even log in. It's just a proxy for the mailing list.

            Obviously this is not a solution for anyone who doesn't have that level of access to their mail server or doesn't have accommodating technicians. It feels like a mis-use of features, it moves a Jira management function (specifying who the email recipients are) outside of Jira which is definitely a bad thing from a maintenance standpoint. You have to remember to keep the members of the mailing list in sync with the members of the Jira group or else it will send email to the wrong people, or not send email to people who should've gotten it. This wouldn't be a problem if the functionality was built into Jira. Not having it makes everything more complicated than it should be.

            Still, this workaround may help a few people in the right circumstances until Atlassian adds the functionality. Being able to mention 'groups' in this way has been very beneficial to our users. Just stay on top of who is in the mailing list.

            Sean M added a comment - - edited I've been creating mailing lists on our mail server for the employees in a group, then creating new unlicensed Jira users with the list's email address. I can mention that user and a notification is sent to the mailing list. A license is not needed since that user will never actually view the ticket – or even log in. It's just a proxy for the mailing list. Obviously this is not a solution for anyone who doesn't have that level of access to their mail server or doesn't have accommodating technicians. It feels like a mis-use of features, it moves a Jira management function (specifying who the email recipients are) outside of Jira which is definitely a bad thing from a maintenance standpoint. You have to remember to keep the members of the mailing list in sync with the members of the Jira group or else it will send email to the wrong people, or not send email to people who should've gotten it. This wouldn't be a problem if the functionality was built into Jira. Not having it makes everything more complicated than it should be. Still, this workaround may help a few people in the right circumstances until Atlassian adds the functionality. Being able to mention 'groups' in this way has been very beneficial to our users. Just stay on top of who is in the mailing list.

            lc43 added a comment -

            gets pretty wild having to get the attention to a particular comment from a team of 3 editors, the pm and dev team, one by one...

            lc43 added a comment - gets pretty wild having to get the attention to a particular comment from a team of 3 editors, the pm and dev team, one by one...

            This seems like such a basic function... yet they have failed to add it.  Must be some other underlying issues with implementing such a basic feature.

            Victor Salazar added a comment - This seems like such a basic function... yet they have failed to add it.  Must be some other underlying issues with implementing such a basic feature.

            dat_alexk added a comment -

            I would also like the ability to tag groups

            dat_alexk added a comment - I would also like the ability to tag groups

            Love to tag groups. When will it happen Jira?

            Deleted Account (Inactive) added a comment - Love to tag groups. When will it happen Jira?

            My company too would like to be able to tag groups of users within a JIRA's comments rather than individual team members. Thank you 

            Josh Jacobson added a comment - My company too would like to be able to tag groups of users within a JIRA's comments rather than individual team members. Thank you 

            Yaroslav Romanov added a comment - - edited

             I would kill for this feature! You know, something small like a carrot. But not spiders, they're icky. 

            Seriously, that would be very useful.

            Yaroslav Romanov added a comment - - edited  I would kill for this feature! You know, something small like a carrot. But not spiders, they're icky.  Seriously, that would be very useful.

            chucktalk added a comment -

            There is a marketplace add-on available to address this for server and DC: https://marketplace.atlassian.com/apps/1219588/mentions-watchers?hosting=datacenter&tab=overview. You can test same for thirty (30) days free and it is reasonably priced from what I see. 

            chucktalk added a comment - There is a marketplace add-on available to address this for server and DC: https://marketplace.atlassian.com/apps/1219588/mentions-watchers?hosting=datacenter&tab=overview.  You can test same for thirty (30) days free and it is reasonably priced from what I see. 

            Any update to whether or not this feature is available? Or whether there's an Add-On option for it?

            Riana Cayabyab added a comment - Any update to whether or not this feature is available? Or whether there's an Add-On option for it?

            +1

            548 votes... 7 years...

            waiting...

            Renato Machado added a comment - +1 548 votes... 7 years... waiting...

            +0.5k votes / 7 years and it is not done yet ?  hm..

            It does not look very hard to code this. 

            Dariusz Nawrocki added a comment - +0.5k votes / 7 years and it is not done yet ?  hm.. It does not look very hard to code this. 

            Sean M added a comment - - edited

            Can we get an update on this please, Jira Server Product Management?

            Sean M added a comment - - edited Can we get an update on this please, Jira Server Product Management?

            @Martin it could be that this solution would cost them as one of the work arounds is to buy another license then link it to an email distro. 

            Louie Garofalo added a comment - @Martin it could be that this solution would cost them as one of the work arounds is to buy another license then link it to an email distro. 

            cannot fathom why this isnt implemented since original request in 2012.

             

            Martin Hilbig added a comment - cannot fathom why this isnt implemented since original request in 2012.  

            The UX feels pretty inconsistent in its ability to @-mention users but not groups.

            Jeremy Nickurak added a comment - The UX feels pretty inconsistent in its ability to @-mention users but not groups.

            oncedadm added a comment -

            +1 pls&thx

            oncedadm added a comment - +1 pls&thx

            It looks like this issue has been open for 7 years now and has over 500 votes. I'm really glad there's a potential App we could use to solve this problem, but it doesn't support JSD 8.0.

            In a large enterprise organization, it's difficult to know who to @mention, but knowing a department or team is much more manageable. Plus, people come and go, while teams are much more stable to be used for inclusion into workflows and processes.

            It's been over a year since the last update on this issue. Is there any chance this functionality might be added into Core in the near future?

            Todd Thomas added a comment - It looks like this issue has been open for 7 years now and has over 500 votes. I'm really glad there's a potential App we could use to solve this problem, but it doesn't support JSD 8.0. In a large enterprise organization, it's difficult to know who to @mention, but knowing a department or team is much more manageable. Plus, people come and go, while teams are much more stable to be used for inclusion into workflows and processes. It's been over a year since the last update on this issue. Is there any chance this functionality might be added into Core in the near future?

              Unassigned Unassigned
              jhammons Jason C. Hammons (Inactive)
              Votes:
              900 Vote for this issue
              Watchers:
              437 Start watching this issue

                Created:
                Updated: