custom fields won't export for different issue type

[alex.webber]

Hi,

We have an issue type in our Jira configuration that doesn't export two specific custom fields that are definitely chosen by Customers when they are first submitted.

This issue type is used when we want to close out tickets and not generate a feedback automation response for Customers so it has a purpose to this end.

What do I need to do to ensure the issue type includes the Custom Fields that I know for a fact were originally selected by the Customer (via Jira Cloud -> Excel exports) ?

Please HELP!

ThanQ,

~Alex

ps. I have chosen the specific aforementioned custom fields from the fields drop down but they are blank as of now.

[Pramodh M]

Hi @alex.webber 

Welcome to the Community!!

Make the field required in Portal View

You'll surely have a field value

If you have the field value, while exporting either choose all fields, or you need to choose the custom field when you export in the list view

Let me know if you have any queries

Thanks

[alex.webber]

Hi Pramodh,

Those two fields continue to not populate even from your suggested JQL / Export Query work around: -

I also see both fields set as required in 'Portal View'.

@Joseph Chung Yin 

Also upon looking under IssueTypes I do see this:

As opposed to 'default field configuration' for Bug (which populates the Business Impact and Application Component fields we want to review), however when I click on the Emailed Issue field configuration view, I see both fields set as Required for Emailed Issue so I'm at a loss as to why those two fields are not populating still...

Thanks for any further insight as to how we can get them both to show within our data exports.

~Alex

[Joseph Chung Yin]

@alex.webber 

Hi Alex:

I cannot read your latest screen captures (the first two) because they are extremely small.  Can you resend them?

On the other note, can you confirm that when customer creates the issue in the portal that he/she always provide values in the fields in question?

Best, Joseph

[alex.webber]

Hi @Joseph Chung Yin 

Reattaching screen captures below via public DropBox links.

With regards to your question:

Can you confirm that when customer creates the issue in the portal that he/she always provide values in the fields in question?

YES, Customers provide these two fields when the ticket is initially submitted as a Bug Issue Type. However, when that Issue Type is transitioned to Support Issue Type (which we do internally) those fields disappear from the Jira Cloud exports for an unknown reason.

https://www.dropbox.com/s/hlrq64d5llpvlil/Jira%20-%20Issue%20Type%20Schemes.png?dl=0

https://www.dropbox.com/s/z31a06usi1ygwex/Jira%20-%20ACA%20is%20a%20required%20field.png?dl=0

https://www.dropbox.com/s/zdsbduimi5km8a9/Jira%20-%20BI%20is%20a%20required%20field.png?dl=0

[Joseph Chung Yin]

@alex.webber -

Thanks for your updated screenshot.  Here is what my understanding of your issue -

1) Customer created BUG issue via the portal and populated both "Application Component Affected" and "Business Impact".

2) Your process converts the BUG issue to Support issue.

3) After the transition, those two fields values are gone.

This is what you need to check - 

• Validate the custom field's configuration that the context setup is assigned to both issue types (BUG and Support) for the same project.
• Validate the field configuration scheme "Emailed Issue" - doesn't have those two fields hidden.
• Validate your internal process that converts BUG to Support is not overriding those fields values or setting them to NULL.

When converting issue type to another issue type, you should ensure that both issue types fields usage are the same and configured the same.  Otherwise, data associated with one issue type may get stripped off after the conversion.

Hope this helps.

Best, Joseph

[Joseph Chung Yin]

@alex.webber -

Welcome to the community.  Based on your ask, you need to ensure that your JQL is querying against the correct issuetype/customer request type since you stated the customers have populated the custom fields in their reported issues.

Once you can confirm the above question, then you can include your custom fields in the search results and then export into Excel output.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.