nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to update a custom field with linked issue type status?

Bruno Xavier_pxa0kl

Please,

I want to grab the linked issue status and show it on a specific custom field.

How can I grab that information, and in addition, the "Assignee" field?

Accepted answers

All comments

Trudy P Claspill

Hello @Bruno Xavier

You can use an Automation Rule to get information from a linked issue and add it to custom fields in the issue to which it is linked.

Do you have any experience with Automation Rules? Here is the home page for the documentation:

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

Bruno Xavier_pxa0kl

Thank you Trudy
I am learning as my project requires, and it is new for me.

Let me check this link

Trudy P Claspill

This scenario is a little more complicated because you are working with linked issues. Are the issues in the same project? If not that adds another element that needs to be considered when creating the rule.

Don't hesitate to ask any questions that come up.

Bruno Xavier_pxa0kl

No that is not the same project.

I have been trying the entire morning with no success, which just makes the custom field "empty" let me paste here what I did

Trudy P Claspill

First thing - if the issue you want to update and the linked issue are not in the same project then you need to create a multiple-project rule. You have to do that from the Global Automation page.

Click the gear icon near your avatar
Click System in the pop-up
In the new screen from the navigation panel on the left click Global Automation.
Click Create Rule
Click on the Rule Details page.
Change the Scope field to Multiple Projects
In the Projects field select the projects that will have the issues you want to update and the linked issues.

Next - for testing purposes using a Manual Trigger is a good idea. Eventually I assume you want that changed to a trigger that will happen automatically, but we will start with the manual trigger. Additional steps and other changes to existing steps may need to happen when the change to an automated trigger is made.

So, let us assume for now that you are manually triggering this rule from the issue you want to update.

Next - we need to figure out which of its linked issues is the one we want to get data from. What is unique about the linked issue that can help us identify it?

Is there only every one linked issue, or could there be multiple issues linked to the one you want to update?
Do you use a unique link type to connect these issues? Could there be more than one linked issue that uses the same link type?
Is the linked issue always in a specific project? Could there be more than one linked issue in that project?
Is there some other identifier that is unique to the one linked issue you want?

Once we figure out what the criteria is for that one linked issue, we need to add a step to get the linked issue. The exact step is going to depend on the criteria we use.

The smart value you tried to use here is not a real smart value. Were you referencing some documentation or post that made you think it was?

Screenshot 2023-09-29 at 11.55.19 AM.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management