Copying fields from an issue to a linked issue

[Anne Farr]

Hi, When linking a ticket I need specific information from the parent issue to be copied over when the linked ticket is created and going to a different project board.  Is there an automation rule that will do this.

Thank You,

Anne

[Thibaut Subra _Elements_]

Hello @Anne Farr 

If you want to go further and are willing to use a third-party application, I can suggest our Elements Copy & Sync app available on the marketplace.

Thanks to our Synchronization recipes, you can associate issues depending on the link types and pass data (summary, description, attachments, comments, etc.) from the source to the target, the other way around or both ways.

Another way to do it with Copy & Sync is to trigger a recipe from the source to clone the issue to the target project (by choosing exactly what do you want to copy and by creating a link between these two issues).

It can improve your processes in many ways and I'll be very happy to help you with that.

Let me know

Regards

Thibaut

[Sanjen Bariki]

Hi @Anne Farr ,

Welcome to Atlassian community!

As per your requirement, It can be achieved by the help of automation.

Please find the below screenshot which I have created in my personal instance.

Please Accept the answer If it helps you 😊.

Regards,

Sanjen Bariki

[Anne Farr]

@Sanjen Bariki Hi Sanjen, I have set the automation rule as you have showed however the information is still not being carried over to the linked ticket.

[Sanjen Bariki]

Hi @Anne Farr ,

Greetings!

Sorry for it.

Could you please try the below attached screenshot automation, I know, It will work propely and i have tested in my trial instance.

In the automation trigger >> Issue linked >> condition ( Branch rule / related issues  ) >> Action ( edit field ) select the field from choose field section then add the smart value like {{destinationIssue.Description}} , {{destinationIssue.Summary}} change as per the requriment field.

 

Please let me know If you have any quries.

Please accept the answer If it helps you 😊

Regards,

Sanjen Bariki

[Anne Farr]

@Sanjen Bariki Hi Sanjen, I have tried that and it still isn't working for me.  Does it have anything to with the fact that the linked issue is a different project from the parent ticket?

This is the only thing I see on the linked ticket

[Sanjen Bariki]

Hi @Anne Farr ,

Can you please share, How you are linking issue and Automation audit log...? 

As I have setup in my instance, it's working properly.

Once again try to only for description what I did in the screenshot. Is that working for only Description.

Note:- the measure think in the automation, you have to add the smart values correctly like your field name.

Regards,

Sanjen

[Bill Sheboy]

Hi @Anne Farr 

To use a rule such as @Sanjen Bariki described to copy fields between issues in different projects, the rule must be either global or multi-project in scope.

Where is your rule defined?  If it is only in one project, the rule scope will need to be changed.

Kind regards,
Bill

[Sanjen Bariki]

Hi @Bill Sheboy ,

The above mentioned rule only for the one project, As per the requriment.

[Bill Sheboy]

Earlier Anne noted the linked issue was in a different Jira project.  That is why I suggested the rule needed a different scope.

If all of the issues involved are in one Jira project, the rule only needs project-scope.

[Anne Farr]

@Bill Sheboy Hi Bill, you are correct the linked issue are in different projects and I do have the rule scope as Global.

[Anne Farr]

@Sanjen Bariki When linking tickets I use the Link issue tab in the original issue

Description is automatically copied over to the linked ticket, I am trying to get additional fields to copy over - and please note that the linked issues are going to different projects and I do have the rule set up as global.

[Anne Farr]

@Sanjen Bariki Are these smart values not correct?  In the audit log I am getting this
Destination issue (to perform actions on this issue use a 'Related branch', you can also access it via {{destinationIssue}}):

[Sanjen Bariki]

Hi @Anne Farr ,

Thanks for your information.

Can you please create the automation globally..?

You need admin access to do the below activity.

Steps:-

system >> Global automation >> create the same automation which i have mentioned above and add only one field for the testing {{destinationIssue.Description}}. For the adition field add the correct field name in the place of Description ( same field name which you have create in the jira ). 

Note :- Above automation will work for the all the projects in the instance like If anyone linked any project then that will copy the parent value So If you need to add for the specific project. Kindly add the condition.

Regards,

Sanjen 

Please let me know the result.

[Anne Farr]

@Sanjen Bariki Hi, I have created the automation globally and I have only added 1 field to test and it is still not working.  Really don't know what I'm doing wrong.

[Sanjen Bariki]

@Anne Farr 

I am sure you are adding the wrong smart values.

Please correct the smart values {{destinationIssue.(copy field name) please add the field name correctly like copy from the custom field sections.what is the correct name.i have tested is working properly.

[Anne Farr]

This is how the custom field is  Steps to reproduce

This is what I have in the Edit issue and I copied the field, it is still not working for me
{{destinationIssue.Steps to reproduce}}

Once I enter the smart value do I need to select SET or COPY?

Thank You,

Anne

[Sanjen Bariki]

Hi @Anne Farr ,

Once I enter the smart value do I need to select SET or COPY?

:- Don't need to click on set or copy, Add the smart value then click on save button.

Regards,

Sanjen

[Anne Farr]

@Sanjen Bariki Thank you for your help but unfortunately it is still not working. 

[Bill Sheboy]

Anne, let's confirm you have the correct smart value for your field...

Smart values are name, spacing, and case-sensitive.  And, smart values do not always match the displayed name of a field on the issue views.

The how-to article below identifies supported smart values.  Essentially the steps are:

• identify an example issue which has your field
• using a browser tab, call a REST API function which will list all supported smart values
• search on the page (e.g. Ctrl-F) to find your field...
  • if you find it, the correct smart value syntax, and custom field id will be shown
  • if you do not find it, the field is not supported by automation rules

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

[Anne Farr]

@Bill Sheboy Thank you very much, I will look into this.  

[Sanjen Bariki]

Hi @Anne Farr ,

I have tested and its working fine.

Kindly reach out to atlassian team they will support you by the screen sharing.

Raise atlassian support ticket .

Regards,

Sanjen

Don't forgot the hit the answer button if it helps you.

[Anne Farr]

@Sanjen Bariki Hi Sanjen, would you be able to show me how you have the rule set up using the field 'steps to reproduce'  not description, description already carries over to the linked ticket. 

Thank You,

Anne