Linked Issues: Create Queue or report?

[Sebastian Santoyo]

Hi, my customer has a very particular need: to see only certain request Types... but displaying fields that belong to OTHER REQUEST TYPES.

On the other hand, I need to display the linked issues again but renaming the column, even if it repeats. 

To have a visual understanding please look at the picture with RED, GREEN AND BLUE stars.

Let us call

BLUE: "law"

GREEN: "requirement"

RED: "task"

I want to display only tasks, the reds. However I want to have available the info of the green and blue custom fields (green & blue hexagons).

The hierarchy is:
A BLUE LAW contains  GREEN REQUIREMENTS and these ones contain RED TASKS (the only ones I want to display in the queue.

Now about the linked issues

you might see the column "Links".
I only want the RED TASKS.
Is there a way I could duplicate the link column but instead of giving me the key "V4-68" it gives me back the name (Summary) of the GREEN REQUIREMENT?

and again...

Is there a way I could duplicate the link column but instead of giving me the key "V4-67" it gives me back the name (Summary) of the BLUE LAW?

and Finally

If this is too complicated, do you think I could handle all this with some sort of report?

[Danut M _StonikByte_]

Hi @Sebastian Santoyo,

I haven't tried it on a JSM project, but it might work to add additional levels to the default Jira hierarchy if you use the Plans feature (aka Advanced Roadmaps) - now available with Premium and Enterprise plans. This would allow you to implement the hierarchy you need and then use the parent-child relationship for all these items (instead of the issue link).

Danut.

[Trudy Claspill]

Hello @Sebastian Santoyo 

With only native JSM function the only method to get what you want would be to copy the information from the blue and green issues into fields within each red issue. And again, with only native functionality, the method to copy the data would be to use Automation Rules.

There are limits to the number of Automation Rules that can be executed each month based on the Subscription being used (Free, Standard, Premium, or Enterprise). The limit could easily be exceeded if the client is using a Free subscription. Otherwise you would need to consider the potential number of rule executions that would occur during a month based on the number of red issues created, and changes in the links between issues.

If the client is open to third party apps there might be other options.

[Sebastian Santoyo]

I am trying with the automation, thanks a lot...

this JQL is not working apparently:
issue in linkedIssues({{issue.key}}, "is blocked by") AND "Request Type" = "Requerimiento SC"

can you please identify what is going wrong?
The copy of the field is not reading the info of the original field..

When I create the "task" I was expecting to have the info filled the info from the filed in the "requirement" request.

[Trudy Claspill]

What output are you getting in the rule's Audit Log when the rule executes?

Make sure to click on the ">" arrows to the right of the messages to expand all the details.

[Sebastian Santoyo]

Thanks Trudy

I am trying to duplicate the content in the fields (GREEN) in the linked issues (RED).

but the output is null, ore "none"... there is nothing in the fields. These fields should "inherit" the info derived from the original issue.

[Trudy Claspill]

Hello @Sebastian Santoyo 

As I mentioned in my previous reply, please show us the output in the Audit Log for the rule. That will provide critical information needed to debug your issue.

1. Can you confirm that the rule is triggered by creation of the RED issue?
2. Is the JQL you have specified is attempting to retrieve the GREEN issues linked to the RED issue?
3. Can you provide a table that shows the field names in the GREEN issue paired with the field names in the RED issue to show which fields you are trying to copy data from and to? In that table also specify the Field Type of each field. Example

Green Field	Green Field Type	Red Field	Red Field Type
Frecuencia	Single Select List	Frequencia de Requerimiento	Single Select List

4. Are you trying to do a straight copy of data? If so, what do you expect to happen if the linked issues have different values from each other?

If the answers to 1 and 2 are "Yes" then your rule is not structured correctly.

When you use a BRANCH (For Each) component and nest actions under it, as you have done with the Edit action, the nested actions are taken against the issues you selected in the BRANCH, not the issue that triggered the rule. So, the Edit action is trying to edit the issues found by the JQL.

Additionally you tried to use the smart value {{lookupIssues}} in the branch to get the value you want to copy. The {{lookupIssues}} smart value is only populated when you use a Lookup Work Items action, which you have not done.

When you more fully describe the details of the fields and scenarios I will be able to offer you more specific guidance.

[Trudy Claspill]

You appear to have replicated this same topic in a new question.

https://community.atlassian.com/forums/Jira-Service-Management/Automation-rule-not-copying-custom-field-values-from-linked/qaq-p/3066258

So I will stop contributing to this post and start contributing to that one.

Having multiple Questions on the same topic makes it more challenging for the responders to build upon each others replies. It is better to have a single Question for your topic.