Versions Compared

Old Version 2

changes.mady.by.user Henry Farris

Saved on

compared with

New Version 3

changes.mady.by.user Henry Farris

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Resolved Issues
  • Known Issues and Limitations

Resolved Issues

Jira Legacy
serverTx3 C7 Jira
columnskey,known issue details,resolution,release notes
maximumIssues20
jqlQueryproject = "VERA Server" AND issuetype = Bug AND "Known Issue" = "Known Issue" AND fixVersion in ("JIRAPP 1.0")
serverIdbae6440d-95b3-3404-9bf8-972dcf0f5081

Known Issues and Limitations

Jira LegacyserverTx3 C7 Jiracolumnskey,summary,known issue details,statusmaximumIssues1000jqlQueryproject = "VERA Server" AND issuetype = Bug AND "Known Issue" = "Known Issue" AND affectedVersion in ("JIRAPP 1.0") serverIdbae6440d-95b3-3404-9bf8-972dcf0f5081N/A

Known Issues and Limitations

KeySummaryKnown Issue DetailsStatus
VS-221Rejection Reason box lingers in the Issues list.The Rejection Reason displayed in the Jira App will persist when other Jira records are selected. The cched rejection reason is removed when the user invokes a browser refresh.SUBMITTED
VS-217Jira web panel hangs on issues without a sync ID.The VERA Approval Route progress spinner and the message "Please wait for VERA to load" is displayed when an issue without a VERA Sync ID is selected from the Issues icon in the Jira sidebar.SUBMITTED
VS-170Rejection Reason is displayed when user creates a sub-task for a jira recordThe Rejection Reason displayed in the Jira App will persist when sub-task records are created. The cached rejection reason is removed when the user invokes a browser refresh.SUBMITTED
VS-139"Pending Tasks" field refreshes too slowly after route withdrawal.The Pending Tasks field in qTest and Jira is not immediately updated when the record is approved or rejected in VERA. The cached values are updated when the user invokes a browser refresh,SUBMITTED