fields that can be copied from JPD idea to Delivery Issue

[CC]

Do you have a list of fields that are currently supported to copy from JPD to Delivery Issue?  I found the automation to copy the description.  I'd like to copy over a few more fields, for example, assignee, team, custom field called "Program Increment".

Trying to front run the complaints I'll hear if our business teams have to enter the data twice.

[Ivor]

I believe any custom field created that is NOT a formula derived field can be copied over by automation with the exception of insights, votes (maybe through smartvalues you could, but I didn't try).

Custom fields, including those existing already in JPD template could be retrieved from automation

[Rohan Swami]

Hi @CC - @Ivor is exactly right here. Thanks Ivor!

[CC]

@Rohan Swami @Ivor Thank You!  Awesome news!  If I find the page that says only description is supported, I'll post it here.

[CC]

@Rohan Swami Could be my lack of experience with automation but I've been trying to copy two fields from JPD to a team project.  The first field (description) copies over fine but I can't get the second one, which is a multi-select custom field, to work.  I think I've tried every possible set up configuration to get it work.  What am I doing wrong?

[Omer Meshar]

There is a known problem that if you have two fields with the same name, one in JPD (which is team based) and one in Jira software, then the automation might confuse the two. I think this is what you are experiencing. Try to change the name of one of them (temporarily) and then configure the rule. Since the names will be different, the rule will not get confused and it should work. Once it works, you can rename back if needed.

[Ivor]

Hi @CC 

Strangely you might be missing a few steps in the automation here - but you might need to add a branching rule first to target specifically the destination issue, but if it works for you then you can omit this.

 

I might be missing some details here but it might be also because that the "Program Increment" field in JPD is separate from the custom field "Program Increment" field in Jira software (if you created the field in JPD).

Take note that these 2 custom fields with their own customfield IDs and with that their own internal value fields for each selection in that field. So it wouldn't work in this situation if you try to copy directly those values.

You would be to map each selection to the applicable value for the both custom fields by appending each selection - in this scenario you need to look at smartvalue manipulations unfortunately.

This is one example of the same use case:

https://confluence.atlassian.com/jirakb/how-to-copy-values-between-multiple-choice-fields-via-automation-1167704702.html

I can't unfortunately do a step by step demonstration, but hopefuly this is enough for you to work it out.

If you get it working it would be helpful to share the end results to the thread here for future reference.

[CC]

@Omer Meshar   that worked!!!  I changed the name on the JPD board and it worked.  Now to come up with a clever naming convention as the fields are the same on both sides.  WOO HOO!!!  One step closer to being able to deployment.  Here is the automation rule. 

[CC]

@Rohan Swami @Omer Meshar @Ivo @Nate Schmidt Potential big bug

I am adding existing JSW issues to a new idea in JPD.  I added the automation as mentioned above and now the descriptions on the existing JSW issues are being overwritten when I "Add a Delivery Ticket" to the idea.  

Ideas?

[Rohan Swami]

@CC looks like the automation is behaving as expected - you're configuring it so that any linked delivery ticket will get the description and the program increment copied across whenever an issue is linked. If you don't want this to happen, then you'll need to turn off the automation.

[Omer Meshar]

@CC if an existing JSW issue already has a description and you don't want it to be overwritten, simply add a condition that first makes sure the description is empty.

[Diana G]

@CCDid you find a solution to it?

[Rohan Swami]

Hi @CC @Omer Meshar @Ivor 

We’re exploring how we can improve this area of the product for customers at the moment, and based on your earlier feedback I’d love to get your input so that we can tailor a solution to your use case. Would you be able to have a short chat with me this week? You can book time in withe me through https://calendly.com/rswami-atlassian/jira-product-discovery-and-delivery

[Omer Meshar]

Hi @Rohan Swami ,

I can't make it today (and not working on Fridays). Would it be relevant to discuss this next week?

[Rohan Swami]

@Omer Meshar I'm on leave next week, i'll reach out again when i'm back if we're still interviewing.