Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,298,527
Community Members
 
Community Events
165
Community Groups

How do I avoid having completed dependency notifications sent to another teams board?

I have created a dependency automation rule that alerts assignees of linked tickets when each ticket is marked as done or cancelled. What I want to happen is that when a team on another JIRA project completes their dependent ticket, our team gets notified. But I do not want the other team to be notified when the dependent ticket on our board is completed.

Is the answer simple as, do not have the dependency automation rule in place on the other teams board?

2 answers

1 accepted

0 votes
Answer accepted

Can you clarify your use case with some sample data and what you expect to have happen? For example:

There are three projects; your project (Project A) and two projects for other teams (Project B and Project C).

An issue in your project (issue A-1) is linked to issues in the other teams' projects (B-1 and C-1), and your issue is dependent on both those issues being completed.

When B-1 is completed, you want (which users on which issues?) to be notified.

Also show us the details of the rule you have set up, and tell us how it is not working the way you want it to work.

When B-1 or C-1 are completed (status of done or cancelled), notify assignee of A-1. When A-1 is completed (status of done or cancelled), DO NOT notify assignees of  B-1 or C-1.

See attached screenshot for details of current automation rule.
dependencyautomationss.PNG

You need to change the For Linked Issues branch to have Type set to only "is depended on by"

Trudy,

Please see attached screenshot.

cgdependencytest.PNG

I updated the rule so that for linked issues it says "is depended on by", but still did not get the result I was looking for in my use case.

When I set the issue on the other teams board (B-1) to done, it should have notified the assignee on the other team for linked issue on A-1, but no notice was ever received.

For reference, the linked issue issue on A-1 was set to "is depended on by" and the linked issue on B -1 was set to "Depends On".

Thank you so much for your help Trudy! I was able to adjust based on your direction and am all set now.

If you look at the Rule Details for this rule there is a section for Scope that names the Project(s) to which the rule will apply. Does this rule specify that it will apply to your projects "B" and "C"? If there are multiple projects that hold the issues upon which issues in project "A" depend, then you will have to make this a Global rule so that you can specify multiple projects within its scope. Otherwise you have to create duplicates of this rule for each "B" and "C" project.

Can you provide images of an issue in project "B" showing its issue key and its Linked Issues section, where the Linked Issues section show the link to an issue in project "A"?

Can you provide evidence of the issue being transitioned from and to the statuses specified in the rule, i.e. an image of the entry in the Issue History that shows the change of status?

When you transition that issue, if this rule is getting triggered than there should be some information about what happened in the Audit Log section. Can you show us what that says?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,869 views 37 49
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you