by Atlassian Labsfor HipChat, HipChat Server 2.2.3 - 2.3.1 and more versions
    Versions available for HipChat Server 1.2.8 - 1.4.3
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Get it nowFree add-on

    Group mention for HipChat

    Group mention for HipChat

    Define an alias

    Easily mention groups of people

    See all aliases

    Use the "/alias set" command to define a group alias

    Use an alias to mention large groups of people with a few key strokes

    See a list of all aliases defined for the room

    Define an alias

    Easily mention groups of people

    See all aliases

    Use the "/alias set" command to define a group alias

    Use an alias to mention large groups of people with a few key strokes

    See a list of all aliases defined for the room

    More details

    There are no additional details.

    More details

    There are no additional details.

    User reviews

    (16)
    Sign in to write a review
    by Scott Moore on 2017-04-21
    At first, we thought this bot was just what we were looking for, until we realized that it doesn't work across rooms. We'd like to define one alias and be able to use it in all our rooms. (I realized that this review just joins the "global aliases, please" choruses from other reviews). Setting up aliases in all our rooms, and especially the transient ones (we have a lot of rooms that are associated with issues we work on, so they are only around for a few days while that issue is in progress), is too much overhead.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Tyler Laing on 2017-02-22
    Global aliases for teams would be great, like many others have mentioned here; however, it would be even better if @someteam (being a global alias) when used within a specific room, could be combined with the @here feature (in some way), so as to only ping the subset of the @someteam members who are 1) actually in the room and 2) are actually here (i.e. not idle, etc); basically a subset of @here. That of course brings up a couple other scenarios for global aliases: pinging all of the members of the global alias regardless of them being in the room or not, and regardless of their idle state (similar to default behavior of @someone); but also it'd be great to be able to @someglobalalias, in a way that only pings those that are already in the room, which would be more like a subset of @all.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Ali Bagheri on 2016-07-15
    some really basic additional commands would help greatly - like being able to add or remove individual members.
    3 out of 3 found this review helpful
    Was this review helpful?YesNo
    by Remi Broemeling on 2016-06-30
    The most disappointing part of this integration is that it is written by Atlassian: it is written by the company actually in a position to implement aliases _correctly_, not by some stand-alone entity that only has access to the HipChat integration API. Aliases (a.k.a. communication groups, chat lists, etc.) should be built directly into the HipChat interface: when mentioning an @group, the message should appear in the channel unchanged, and the @group should act as an @-mention for all of the people in the group. Atlassian can do this -- no-one else can, but Atlassian can. Instead of doing that, Atlassian gives us "AliasBot", which is awful. It appears to be more of a tech demo of their integrations than something actually useful or usable. - by echoing the same message back to the room with the alias replaced by the recipients, AliasBot effectively halves the Signal-to-Noise ratio of the communication that it is involved in. - AliasBot _obviously_ doesn't scale: large groups of recipients end up with dozens (or more) of @-mentions in the text, which makes a horrible mess of what is supposed to be a communications medium. - AliasBot is non-global: an alias setup in one room is not accessible in other rooms. This is very ambiguous and confusing, as the standard way that we would like to use these aliases is to convey departmental (or team) membership, and those very much transcend room boundaries. This is an add-on that would be poor if an external entity published it. For Atlassian, the company directly in the position to actually solve this problem correctly, it is just inexcusable.
    17 out of 17 found this review helpful
    Was this review helpful?YesNo
    by Patrick Zahnd on 2016-04-07
    [could be optimised] It multiplies messages and in the multiplied message, it mentions each member in the alias. However, it should rather work like e.g. the @all alias. [feat req +1] If possible, the aliases should show up in the tab-completion list. [feat req +1] Global aliases, preferably linked to AD groups so membership is maintained automatically. [feat req +1] To have the ability to add global aliases (while still having local aliases). So @teamname should work across all rooms, if added as a global alias. This feature is so much needed, it should actually be implemented into HipChat itself.
    3 out of 3 found this review helpful
    Was this review helpful?YesNo

    Pricing

    Basic support resources are available for this add-on.

    Basic support resources are available for this add-on.

    Vendor support resources

    Documentation

    Find out how this add-on works.

    Community

    Community discussions connect you to the vendor and other customers who use this add-on.

    Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this add-on.

    Documentation

    Find out how this add-on works.

    Community

    Community discussions connect you to the vendor and other customers who use this add-on.

    Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this add-on.

    Versions

    HipChat Cloud Released 2017-04-07

    Summary

    Aliases are now case-insensitive

    Versions

    Version 1.3.2-AC HipChat Server 2.2.3 - 2.3.1 Released 2017-04-07

    Summary

    Aliases are now case-insensitive

    Installation

    1. Log into your HipChat instance.
    2. From the main horizontal menu, click on Integrations. The integration screen loads
    3. Locate Alias. The screen contains add-on versions compatible with your HipChat instance.
    4. Hover over the add-on and click the + symbol to install. Then follow on-screen instructions. If your add-on can only be installed by an administrator, you will see a prompt. Otherwise, choose a room you own to install the add-on.
    5. You're all set!

    To find older Alias versions compatible with your instance, you can look through our version history page.

    Click on Get it now to be redirected to your HipChat instance to install this add-on. Then follow on-screen instructions. If your add-on can only be installed by an administrator, you will see a prompt. Otherwise, choose a room you own to install the add-on.

    Similar add-ons