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.