Hello all,
I would like to address the following use-cases:
1. Keeping key stakeholders updated each time a new sprint starts with the exact content of whats in the sprint
2. Similarly keep stakeholders updated each time a release is deployed with the exact content of whats in the sprint
Our organization uses slack for all communication so I would like to enable the following flow:
1. Each time a new sprint starts a message is sent to a given slack channel with a list of
all tasks
2. Each time a new release is deployed a message is sent to a given slack channel with a list of all tasks
Is this possible?
Yes, it is possible, and you can do this with automation. The first automation would be triggered on sprint started, then use a lookup issues for that sprint and then send the Slack message like this:
The second automation would trigger on version released.
@Mikael Sandberg thanks for your answer!
In this final stage of the automation how can I iterate through all of the stories captured in step two and display the titles and ideally links to the jira as the body of the slack message?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can, but a better option would be to use the list feature to list them, lookup issues will return a list of issues and you can use that to create the list directly in the message like this:
{{#lookupIssues}}
* {{key}} {{summary}} {{url}}
{{/}}
You find out more information about using sections and list with smart values here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mikael Sandberg thanks so much this was super helpful!
1. Is there a way to get the name of the sprint for the slack message?
2. Would you be able to explain the logic of the syntax you provided so I can learn how it works?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@ABD You should be able to get the name by using {{sprint.name}}, and you can learn more about the logic of the syntax I provided if you check out the link in my post above.
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.