The Jira vocabulary seems very limited. And I don't find the Jira Create Flow UI very intuitive. Any guidance would be appreciated.
Hi, @William T Dixon Not sure what you mean by "Create Flow UI". But if you want to send a notification about a resolved blocker, you can make an Automation rule:- Trigger: Issue transitioned to Done, or Resolution field is changed (fires on the blocker itself)- Branch: For linked issues, link type "blocks" (these are the issues your blocker was blocking)- Inside the branch, Action: Send email to assignee, or Slack message, or comment on the issue, whatever channel you like
One important thing to watch: the link direction. On the blocker the link is "blocks", on the dependent issue it's "is blocked by". The rule runs on the blocker, so branch over "blocks".
Hi @William T Dixon !
I completely agree that setting up notifications directly inside project workflows or creation flows isn't very intuitive!
The most flexible and effective way to handle this in Jira is by using Automation. Here is how you can set it up in a few simple steps:
This gives you full control over who gets notified without needing complex workflow configurations!
Hope this helps!
Hi @Evgenii
Automations are now on creation mentioned as a Flow instead of a Rule.
No idea on why this has changed!
Further more you are right on the guided setup.
Hi, @William T Dixon !
Evgenii's rule covers the blocker reaching Done. The rule most teams need next is the one for when the blocker slips: trigger on "Field value changed" for Due date, branch over the blocker's "blocks" links, and add a comment on each waiting work item, something like {{triggerIssue.key}} is now due {{triggerIssue.duedate}}. Use triggerIssue there, because inside the branch issue is the waiting item. That way the waiting team hears before the date arrives, not after.
{{triggerIssue.key}} is now due {{triggerIssue.duedate}}
triggerIssue
issue
Atlassian's own request for this kind of notice, JSWCLOUD-9039, was closed for low engagement, so automation is the native route for now.
Full disclosure, I'm the developer of Blockline, and it won't send that notification: it notifies no one. What it does is put the answer where the waiting team already looks. Each space gets a tab listing its epics with what they wait on and why in one line ("PAYC-3 blocks STOR-4 · lands 15 Dec · 6 days after this epic's date"), and once the blocker is done its flag clears. So the rule does the telling, and the tab is where the team checks what they're still waiting on.
@William T Dixon if you'd rather not build and maintain that rule in every project: Disclosure, I built Dependency Guard for Jira, and this is one of the things it does without any rule. When a work item is done, every work item linked to it with "is blocked by" that isn't done yet gets a comment, so its assignee and watchers are notified the normal Jira way. A panel on each work item shows which blockers are still open, and the notification can be switched off per project. It only looks at "is blocked by" links, not other link types. Free for up to 10 users: https://marketplace.atlassian.com/apps/3010916545
It looks like you're new here. Sign in or register to get started.