Can I customize the returned fields of jira connector?

[Szentkiralyi_ Rikard _PNA_]

The Jira connector provides a predefined list of fields it can return when using actions such as Get issue (V2).

My question is whether it is possible to customize which fields the connector retrieves and returns, or if this is fixed. The goal is to read an issue from Jira and populate a template with only specific fields. However, based on the current response, the connector is returning only a subset of fields, most of which are not needed.

I am assuming this behavior may be related to the fact that our issue creation template differs from the default Jira template.

[Tomislav Tobijas]

Hey @Szentkiralyi_ Rikard _PNA_ ,

Not sure for v2, but in v3 (GET Get issue), you should be able to use query parameter fields, where you can then specify fields so not all of them are returned.

For example

GET /rest/api/3/issue/{issueIdOrKey}?fields=field1,field2

I'm curious, which fields are not returned when you use v2? Did you notice specific field types missing or any other pattern?

Cheers,
Tobi

[Szentkiralyi_ Rikard _PNA_]

Hi Tobi,

So I think because our jira template is custom that's why Get Issue v2 is not returning the fields I'm looking for. Which means I will have to build a custom solution to achieve my original task. I'm looking at using Rest api connector instead. 

Best,

Rik 

[Himanshu Tiwary]

Hi @Szentkiralyi_ Rikard _PNA_ ,

not in the standard connector action.

Get issue (V2) returns a fixed response schema from the connector, so you usually can’t choose which fields it fetches/returns there. That behavior is not driven by your issue create template.

If you only need specific fields for a template, the usual options are:

use the connector as-is and map only the fields you need downstream, or

call the Jira REST API directly, because that supports requesting specific fields only.

Also, if some expected fields are missing, check whether they are:

actually present on that issue type/project

visible to the account used by the connection

So the answer is: the connector output is basically fixed; selective field retrieval requires the Jira API, not the built-in action.
Referance Doc : https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/

[Szentkiralyi_ Rikard _PNA_]

Hello Himanshu,

I'm working on this right now thank you. 

Best,

Rik