I am working with multiple projects and I want my Issue in one project to transition from one status to the next based on the status of it's linked issue from another project. I cannot seem to find any information on how to view the status of the linked issue in order to make my automation.
Hi @Joe Sherman and welcome to the Community!
An automation rule needs a trigger and - in the case you describe - the most logical one would be the issue in the linked project transitioning into a certain status.
The rule also has a scope, which you can find in the rule details. In this case, it is essential that you include both projects that contain the issues (or more projects if that is relevant for your use case).
Starting from that base, your rule should look like this:
The second step (issuetype = Task condition) is optional, but I added to show that you can narrow down on the cases when to execute the rule or not.
In the For Linked issues (this is a related issues branch) I only select issues linked with the Implements link, which is also configurable.
Hope this helps!
Adding to this...
Note that a multiple-project scoped rule can be created only by a full Jira Administrator.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am very new to Jira and this is what I have been trying to do. I am trying to look at the status of my linked issue and then transitioning the issue in my project to a new status. We do not have a specific Jira Admin here at my company working on things like this. I wont be able to get that accomplished through that person. That is why I am trying the scheduled trigger. Am I going in the correct direction?
Basic steps are below.
Look at issues with status of "Release Backlog"
Look at linked issues linked by "is implemented by" with status of "Verification"
Transition issue from "Release Backlog" to "Update Genius"
I believe my problem or error is the status of my linked issue equaling "Verification" doesn't work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have full Jira Administrator access?
Do you see a gear icon next to you avatar in the upper right corner?
If so, when you click on that gear icon do you see an option for System?
If you don't have a gear icon or don't have the System option under it, you will not be able to create the automation that you need.
In order to accomplish your requirement of updating issues based on issues in an entirely different project you must create a rule that has multiple projects specified in its Scope on the Rule Details page. That can only be done from the Global Automation page, and that page is only accessible to full Jira Administrators.
Without the full Jira Administrator access you are able to create rules that will act on issues only in a single project and cannot use references to issues in other projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, so I have access now. Most likely for a limited time. Can you help me with what I would need to do to accomplish my automation? Or point me in the correct direction to learn how to accomplish this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Joe Sherman -- Welcome to the Atlassian Community!
For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!
Until we see those...
When do you want this transition to occur? For example, based on a transition of the linked issue first?
If so, you may be able to just branch to the specific linked issue. If not, you may need to either access the issue data through its smart values (e.g., inwardIssue or outwardIssue) or by first getting the issues using the Lookup Issues action.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am pretty new to Jira so I do not know if I am doing this correctly.
Does this help?
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.