• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Notifications
    • None
    • 3
    • 1
    • 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.

      Currently Bamboo generates mail notification with subject like:

      "[Bamboo] <Full Project Name> - <Full Build Plan Name> build <Build> was SUCCESSFUL (with <Number> tests). Change made by <User Name>"

      Such subject is really long and complicates subject reading for developers. Also some useful features are missing in mails. Could you please implement the following really simple enhancements? They are really simple to do:

      • Provide option to put short build name into subject instead of full project and build plan name. For example to have something like "[Bamboo] PRJ-PLANNAME-NUMBER was SUCCESSFUL (with <Number> tests). Change made by <User Name>"
      • In case of tests failures it is really nice to see total number of tests and number of failed tests in the subject. It can be also optional. For example "...XX tests out of YYY failed...." or "...XXX/YYYY...". Or failed or successful tests percentage can be added.
      • Provide an option to set mail importance depending on build/test result. All failure messages can be sent with high importance and success mails can have low importance flag. Doing this will help to easily see the status in mail applications like Outlook. We had such a feature in custom build server and it was really useful.

            [BAM-3253] Ability to modify Bamboo mail subject line

            +1 for the ability to change the subject, but in my case for notification about comments.  Or even just for changing the default.  This:

            "[Bamboo] PersonName commented on xxxx - testname build #100"

            means that email clients do not thread the comment chain, since every person who comments generates a unique subject.

             

            Tim Burgess added a comment - +1 for the ability to change the subject, but in my case for notification about comments.  Or even just for changing the default.  This: " [Bamboo] PersonName commented on xxxx - testname build #100" means that email clients do not thread the comment chain, since every person who comments generates a unique subject.  

            Dave Cox added a comment -

            We use variables to apply build numbers to the components we build, and coordinate those numbers across Bamboo plans and branches. Thus the Bamboo build's notion of build number doesn't correlate to our product build numbers. Our integrators, testers and users are concerned with the latter. So I would like to put the latter, derived from a variable, in the notification email subject and body. So, please allow incorporation of variable values in the email subject. Also, it would be nice to customize the notification email body more easily than editing the freemarker templates in the server filesystem.

            Dave Cox added a comment - We use variables to apply build numbers to the components we build, and coordinate those numbers across Bamboo plans and branches. Thus the Bamboo build's notion of build number doesn't correlate to our product build numbers. Our integrators, testers and users are concerned with the latter. So I would like to put the latter, derived from a variable, in the notification email subject and body. So, please allow incorporation of variable values in the email subject. Also, it would be nice to customize the notification email body more easily than editing the freemarker templates in the server filesystem.

            I just realized I could only customize the notification body and not the subject. This would be extremely useful.
            Until this enhancement is implemented, you guys should really update the Bamboo/Freemaker notification to make it clear that only that body of the notification can be modified with Freemarker templates.

            David Corley added a comment - I just realized I could only customize the notification body and not the subject. This would be extremely useful. Until this enhancement is implemented, you guys should really update the Bamboo/Freemaker notification to make it clear that only that body of the notification can be modified with Freemarker templates.

            Yes, if we had the ability to configure the order of parts in the subject line that would be very helpful.

            I would personally like to see the subject as
            [Bamboo] <Build Result>: <Full Project Name> - <Full Build Plan Name> build <Build>. Change made by <User Name>

            Most of the time the combination of project and build plan name are too long and you never see the Success vs Failed part so unfortunately a lot of the build failures get ignored until i yell at someone. Having the ability to set the "High Importance" flag as well would be icing on the cake.

            Kristopher Keller added a comment - Yes, if we had the ability to configure the order of parts in the subject line that would be very helpful. I would personally like to see the subject as [Bamboo] <Build Result>: <Full Project Name> - <Full Build Plan Name> build <Build>. Change made by <User Name> Most of the time the combination of project and build plan name are too long and you never see the Success vs Failed part so unfortunately a lot of the build failures get ignored until i yell at someone. Having the ability to set the "High Importance" flag as well would be icing on the cake.

            DaveT added a comment -

            Ability to customize the email subject line would be great. In the current form, notifications for failed builds aren't always noticed by our development team. It would be nice to make these emails stand out a bit more.

            DaveT added a comment - Ability to customize the email subject line would be great. In the current form, notifications for failed builds aren't always noticed by our development team. It would be nice to make these emails stand out a bit more.

              Unassigned Unassigned
              fd413da8f5ef Sergey Pimenov
              Votes:
              14 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: