Advance Query Reports - Schema Changes with v8.6.4

Refer to the below updates that affect the database schema of the Advance Query Reports.

1 What is getting changed?
2 Why is this getting changed?
3 What is the impact and what needs to be updated?
4 Which tables and fields are changed?

What is getting changed?

With QMetry v8.6.4, two tables requirements and issues in the reports schema will have Jira integration specific fields renamed to more generic names.

Why is this getting changed?

This change is being made to accommodate the changes in the future version 8.7 which introduces integration support with Azure DevOps and Rally.

In the current version the supported integration is only Atlassian Jira, hence the Jira fields are prefixed with jira<fieldname> in advance query reports schema.
With the integration support now being extended for Azure DevOps and Rally, the same fields from Issue and Requirement module tables will be utilized for all supported external system integrations and the prefix jira is replaced with ext to make it more generic regardless of the integration system. This will also help users to distinguish QMetry fields and External integration fields with ease.

What is the impact and what needs to be updated?

After 11^th October, 2020 - post upgrade to QMetry v8.6.4 on Cloud OR when Server customers upgrade to this build,

You DO NOT need to update any of your existing queries or gadgets to see the output, and they will keep working as before. Field name changes would be automatically taken care at the time of the upgrade to v8.6.4 for both Cloud and Server users.
- Any requirements or issues table fields as below prefixed with jira would have updated prefix as ext
- Any requirements or issues table fields aliases having keyword “jira“ would be updated to “ext“.

However, there would be instances where any query aliases that had the word “jira“ would be replaced with the word “ext”. If you want to continue seeing “jira“ in the alias names, you would need to manually rename/update them back to “jira“. This does not impact the logical output of your query in any way.

Which tables and fields are changed?

Insights Table	Current Field	New Field

Insights Table	Current Field	New Field
issues	jiraCreatedBy	extCreatedBy
	jiraID	extID
	jiraKey	extKey
	jiraOwner	extOwner
	jiraProjectID	extProjectID
	jiraProjectName	extProjectName
	N.A.	extIntegrationType
	N.A.	extConfigurationAlias
requirements	jiraAffectedVersion	extAffectedVersion
	jiraComponent	extComponent
	jiraCreatedBy	extCreatedBy
	jiraCreatedDate	extCreatedDate
	jiraDescription	extDescription
	jiraEntityTypeID	extEntityTypeID
	jiraEntityTypeName	extEntityTypeName
	jiraEnvironment	extEnvironment
	jiraFixVersion	extFixVersion
	jiraID	extID
	jiraKey	extKey
	jiraLabels	extLabels
	jiraOwner	extOwner
	jiraPriority	extPriority
	jiraPriorityID	extPriorityID
	jiraProjectID	extProjectID
	jiraProjectName	extProjectName
	jiraReporter	extReporter
	jiraResolution	extResolution
	jiraStatus	extStatus
	jiraStatusID	extStatusID
	jiraSummary	extSummary
	N.A.	extIntegrationType
	N.A.	extConfigurationAlias

For any questions or concerns feel free to reach out QMetry Support by sending an email to qtmprofessional@qmetrysupport.atlassian.net.