Are you interested in how an enterprise Jira Cloud instance manages dependencies between several vendors? Join us on Thursday, June 16th from 1:00pm - 2:00pm MT to learn more!

DISH Wireless has a unique use case that made this workflow a fun challenge for our Jira team.

DISH works with dozens of vendors, and the nature of this work is often proprietary and requires work from Vendor A to be hidden from Vendor B, while still being accessible by DISH. While vendor backlogs need to be kept private, sometimes Vendor A has a dependency on Vendor B. This is where our new dependency workflow comes into play.

Using JMWE, ScriptRunner, and Global Automation the team has come up with a scalable solution that allows Vendor A to create a dependency on Vendor B that is visible, but still maintains security requirements that require vendor backlogs to be hidden from other vendors.

We welcome you to join us for a demonstration of this process and a Q&A with our admins who created this workflow.