Associating Custom Fields from JPD to Software Project

[Abby Kiesling]

I am trying to create an automation where, when an Idea in JPD is transitioned to "Selected for Development", a ticket is automatically generated in my engineering software project, but I am unable to make this work due to custom fields that are required in the software project.  Additionally, I want to include some important fields from JPD into my software project.  

The issue I'm running into is that Jira doesn't know that Field A in my JPD project is the same thing as Field 1 in my Software Project, and I cannot for the life of me figure out how to code JSON to make it work.  

I should also note, I can find the custom field ID for the software project fields, but I can't figure out how to get the IDs for my JPD fields. 

[Hermance NDounga · Accepted solution]

Hi Andy, 

basically this functionality is a WYSIWYG exporter, so it's not planned to have the description in it (especially since the description can be _very_ long and including a lot of formatting, attachments and links, which aren't suitable to the csv format. 

The main usecase was to be able to quickly get and export to then do even more complex operations, such as advanced filtering, or pivot tables, based on formula values etc. 

Could you please elaborate on your use case? 

In the meantime, you can display a short text field , such as "public description, which will be useful also for timeline views or when we release stakeholder views. 

Cheers, 

Hermance

[Andy Lutz]

Thank you Hermance, that was what I assumed and I appreciate the clarification.

For my use case specifically, I have several PMs that want to share an export with other stakeholders who do not have access to their Project. However, without the Description, the stakeholders don't have the additional context needed to make the export useful.

I'm curious when stakeholder views is planned for release?

That might solve part of this issue.

[Hermance NDounga]

Hey Andy, 

Yeah for what you describe, sharing static csv documents isn't ideal anyways. Stakeholders view is currently EAP, so I cannot provide you with an exact date, but it should be in like 3-6 months :) 

[Sebastian Pechhold]

Descriptions will be exported as well. After export you can check the file and before importing them, you can validate all data. It is not really easy but feasible.