Page Comparison

...

• 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.

...

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

• You would need to update any query aliases having word “jira“ again, as they would be seen replaced with word “ext“. However this does not impact the logical output of your query in any way.You do not 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?

...

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