Changes to the Jira data schema

[Carlos Andres Lopez Ayala]

Good morning,

Since the change to the term "Work" was officially published, the change has been identified in the Jira for Sheets connector. However, today I'm returning to the original Issue definition.

Is this a temporary error, or what will the actual name of key fields like "Issue Type/WorkType" be in these types of connectors?

[Andy Heinzer]

Hi @Carlos Andres Lopez Ayala 

I have not yet found any other reports of this revision.  But perhaps there is a problem with the Jira Cloud for Google Sheets app.  I have created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-1120762 so that our team can investigate this further.

Andy

[Carlos Andres Lopez Ayala]

Okay, how long will it take for you to get an answer on this?

[Valerie Knapp]

Hi @Carlos Andres Lopez Ayala , welcome to the Atlassian Community and thanks for your post. 

Are you saying you don't get any results with a JQL query with the change of the definition? 

Can you show us what you mean? You can anonymise any sensitive information. 

Best wishes

[Carlos Andres Lopez Ayala]

Hi @Valerie Knapp , 

The JQL query continues to return consistent results within the JIRA connector for Google Sheets.

However, with the recent changes to "WorkType," the field names (headers) in the resulting table have changed.

For example, since the change, the name of the "Type" column was "Worktype," but today the table displays "IssueType" as the column name again.

These changes cause conflicts in subsequent automations using the query's resulting table in Google Sheets.

[Valerie Knapp]

Hi @Carlos Andres Lopez Ayala , thanks for clarifying. I will tag the Atlassian support into this post because I don't know what to advise. They will reply here directly.