Hi everyone👋
I’d like to proceed with setting up custom automation for sending messages from Jira to the Slack channel, but I face problems with writing proper message that will provide necessary release notes by using smart values in Jira.
Basically, I need a message that is following the conditions and rules outlined below:
Release Note Information:
• Release note for PREPROD deployment: <link of CW2024-43>
• Release note for PROD deployment: <link of CW2024-41>
3. Rules:
Please let me know if you need any additional details or clarification.
Thank you for your time and support!
Best wishes,
Bilal M.
Hi @Bilal, You might also want to explore our app, Automated Release Notes and Reports for Jira. With our visual template builder, you can create professional Slack messages that incorporate field variables and other visual elements. The app's automation rules allow you to trigger templates based on events in Jira, such as 'Version-Release' or 'Sprint Completed.' Plus, we offer a free version to help you get started right away!
Here is a quick video guide for your reference: https://youtu.be/8W6NKtTMRcI?si=PYHo97iikIQkfIkO
Regards,
Sujeet
Hi @Sujeet Pathak
I am also aware of your good app and unfortunately, I can't apply it because I have to take it in count of budget and get approval from upper management, but thank you for response. You are app is really good for its purpose.
Thank you!
Bilal M.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bilal , I’m glad to hear you’re familiar with the app and that you liked it! Just so you know, we also offer a “free” version available in the marketplace (here’s the link - https://marketplace.atlassian.com/apps/1223567/free-ai-powered-automated-release-notes-reports-for-jira?hosting=cloud&tab=overview). This free version includes all the features of the paid app, although there are some limitations on monthly rule executions. If that works for your needs, feel free to give it a try!
Regards,
Sujeet
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bilal -- Welcome to the Atlassian Community!
What have you tried thus far to solve this need?
If you have a rule and it is not working as expected, context is important for the community to help. Please post the following:
If you have not started a rule, please note the Atlassian Community is a place for people to learn and collaborate with one another. It is not a free source of labor to implement solutions for specific requests. Please contact your Jira Site Admin to help with such requests.
I suggest you try creating the rule, and if you run into challenges, please post what I noted above to ask for help. To get you started on creating your rule, please refer to these documentation and example sources:
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There are also various third party apps that allow you to publish release notes to Slack, with a lot more flexibility.
Although not fully automated, like you mentioned, apps like Released[1] are able to generate release notes with AI and allow you to publish to Confluence or a central portal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jens Schumacher - Released_so and @Bill Sheboy
I am totally aware with purpose of this community and tried many smart values from documentation; however, I couldn't achieve what I was looking for and that's why left such long message explaining what I needed.
Unfortunately, I can't use any third parties, it will require long process behind that I want to avoid having by using automations and webhook already provided. I created several test automations and come up with most working one where I trigger it by ending active sprint. The trigger name - New unreleased note. As the next step I have sending message action to slack with such content (ignore trigger for now, I selected it in purpose for testing):
As you can see I am not receiving any information from smart values taken from documentation and I will appreciate any help or guidance upon this automation. This what I can tell you about project or information that I can provide for public view.
Thank you again!
Best wishes,
Bilal M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Automation issues are hard to debug remotely.
What are you seeing in the audit log?
It appears that he values are not available. Is the issue defined in the trigger?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bilal 👋,
As mentioned by @Jens Schumacher - Released_so {{issue}}
won’t return any value since the automation is triggered when the sprint is completed. This happens because the trigger doesn’t inherently associate a single issue with the sprint closure.
To address this, you’ll need to add a Lookup issues action to fetch the issues before accessing the relevant version details.
🎯 Tip:
If the automation is specific to a single Jira project, you can skip adding a JQL condition in the rule. Instead, define the project scope directly in the automation’s Rule details.
Hope this helps! 😊.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Bilal -- thank you for the screen images.
Adding to what @ALAA EDDINE ROUCADI notes, the rule image you show does not show the Sprint Completed trigger. Did you post the correct rule image?
When using the Sprint Completed trigger, and wanting to report on a version from one of issues in the sprint, the rule could:
Please also consider: if your issues have been in multiple versions, the Fix Version field could contain multiple values. Thus you will need to consider which one to examine for the condition tests.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you so much for tips and suggestions @Bill Sheboy and @ALAA EDDINE ROUCADI
I will try to apply them and I will update you about result.
For the fix version I was thinking to create a new automation that will rewrite fixed version for all issues in active sprint once it started so at the end all those issues will correspond to right release note
Warm regards,
Bilal M.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.