Our process regularly has dependent work from another team/project. I would like to be able to setup a rule where once the linked issues from their project are done we can transition the state of our issue.
There are at lest two possible ways to do this (with automation for jira)
1. create a global automation rule triggers on transition and add an „if“ statement to check whether the issue is in project A so you can transition the linked issues in project B. To do this you need system admin rights.
2. create a project rule in project A that is triggered by transition. In this case you can live without the „if“ statement and do the transition in project B. To do this you need project admin rights in project A.
In both cases you need a branch rule find the related issue(s) in project B. Inside of the branch rule you can do the transition.
In both cases the rule should run under the credentials of a user with transition permission in project B. We have a dedicated „automation-user“ which has permissions for all projects.
Join PM Evangelist, Axel Sooriah, & Product Ops. Consultant & Advisor, Jenny Wanger, as they unpack the role of product ops and discuss key takeaways in Atlassian’s ‘The Product Ops Mission’ guide. They’ll answer your questions live on May 6 at 9:00am PT.
Register here ⬇️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.