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; } } }

Issue Linking - Copy Value from B to A

Mateusz Janus_emo9ao

Hello Brothers and Sisters,

i am jira server...with JMWE plugin (just in case). The scenario i am fighitng below:

1. Ticket A is raised under Project X

2. Ticket A is "DONE"
3. Automatically I create Ticket B under Project Y

4. Automatically Ticket A and Ticket B are linked with "X Related/Y Related" link

Issue: Linking is not a good source of information. The perfect solution would be
1. When Ticket B is created copy B-Key number to ticket A (dedicated custom field) using condition "when Issue Linked is " Y Related". All required data are already there when ticket B is created i just need to somehow copy B-Key number to ticket A.

I was trying with JMWE and Automation but already lost hope...

Accepted answers

Trudy P Claspill

Hello @Mateusz Janus

How are you creating the new issue? Are you using an automation rule or a workflow post function?

What have you tried for copying the key for the source issue to the destination issue?

If you have tried an automation rule please provide screen images showing us:

The entire rule
The details of each step in the rule
The details from the rule execution log for when the rule ran

All comments

Trudy P Claspill

Hello @Mateusz Janus

How are you creating the new issue? Are you using an automation rule or a workflow post function?

What have you tried for copying the key for the source issue to the destination issue?

If you have tried an automation rule please provide screen images showing us:

The entire rule
The details of each step in the rule
The details from the rule execution log for when the rule ran

Mateusz Janus_emo9ao

Hey,
so it looks like below (unfortunatelly i am not allowed to upload anything - cybersecurity)
1. Issue A is RESOLVED
2. using Post functions I create Issue B with issue linked to issue A
3. Issue Linked is "X related/ Y Related" so Issue B is X realted to Issue A

A-123 is linked "Y related" with B-123.
B-123 is linked "X related" with A-123.
Till this moment everything is automatically done with post functions.
Now i am wondering HOW to reflect B-123 reference in A-123.

Trudy P Claspill

Are you using a JMWE post function to create the issue?

What version of JMWE are you using?

The JMWE Create/Clone Issue post function supports setting values in fields of the new issue by using Groovy script, which would enable you to set a field to the key of the source issue.

https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461472239/Create+Clone+issue+s

Mateusz Janus_emo9ao

hey @tru

1. YES i use JMWE post function to create issue B under project Y.
2. Issue B is CLONE of issue A under project X.
3. I DO CLONE issue A key and put into Issue B
4. I DO also linking "Issue A is 'Y related' with issue B" and "Issue B is 'X related' with issue A"

The problem is if we call issue B as Destination Ticket, when issue B is finally created (with this JMWE post function) issue B gets jira KEY value i.e. B-123. And I need to now copy this Key B-123 to issue A. (source ticket).

So its cloning value from B to A.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-data-center

data-center

linked