Vivid Trace 2021.1 Specifications

A deployment of Vivid Trace consists of Vivid Trace for Jira, and optionally Vivid Trace for Confluence.

Jira: Hosted versions of Atlassian Jira which include Jira Server, Jira Core, Jira Software, Jira Work Management, and Jira Service Management, starting from Jira version 9.4. Jira Requirements also apply directly to Vivid Trace, including supported browsers and devices. The only additional requirement made by Vivid Trace for Jira is that the Issue Linking feature is enabled in Jira. This feature has been enabled by default in new Jira installations since Jira version 9.4.

Confluence: Hosted versions of Atlassian Confluence Server, starting from Confluence version 7.4. Confluence Requirements also apply directly to Vivid Trace, including supported browsers and devices. Refer to the documentation for the Confluence Add-on Software for further requirements.

Vivid Trace is available for Confluence Server, Jira Server, and Jira Data Center. It is not currently available for Atlassian Cloud.

Vivid Trace supports issue types, sub-task types, issue link types, and certain issue fields packaged with Jira, the following Jira add-ons, your own custom types created manually using the administration pages bundled with Jira, and further integrations.

• Atlassian Confluence Server
• Atlassian Jira Software
• Atlassian Jira Service Desk
• Tempo Timesheets
• Xray for Jira
• Zephyr for Jira

The following table lists the localizations included in the add-on software and degree of completeness expressed as a percentage (%) of the quantity of localization keys, as well as availability of localized product documentation and support.

Vivid Trace's open translation management system welcomes improvements and new language contributions.

Within the add-on software, incomplete portions of a particular localization are filled in with resources sourced from the default language setting in Jira's internationalization preferences. All language resources stored within the add-on software use Unicode encoding.

Vivid is committed to being a long-term island of stability and transparency.

We take pains to avoid changes to shipping features that would force customers to incur retraining costs.

Shortly after a new major or new minor release of Jira, an updated and tested version of Vivid Trace is made available as necessary via the Atlassian Marketplace so that Jira systems can be easily updated using Jira's Universal Plugin Manager (UPM). The exact timing of release varies, as it depends on Vivid's organizational capability, changes in new Jira releases, and changes made by Atlassian to its add-on development program, among other factors.

Compatibility with older Jira releases is dropped only when maintaining compatibility becomes acutely economically unviable, or in the face of acute technical difficulties.

Due to varying levels of adherence for web standards in supported web browsers, users of supported but older, partially incompatible web browsers such as Microsoft Internet Explorer 9 might experience functional and visual degradations.

A primary value of Vivid Trace is realized through comprehensive visualization of large amounts of data for efficient processing by the human eye. Although Vivid has made some affordances for universal accessibility, we have not developed a comprehensive method of translating the visual experience into one where a potentially overwhelming amount of issue and relationship detail can be efficiently described through a screen reader or other assistive device.

Affordances for Universal Accessibility:

• Color is used sparingly, adhering to the Atlassian Design Guidelines (which considers universal accessibility concerns), and otherwise deferring to established precedent in recent Jira releases.
• Vector-based visuals are employed, wherever pragmatic, because they can be cleanly enlarged without pixelation.
• Textual information is kept trimmed down to key meanings so that text-to-speech systems can better identify and more efficiently synthesize information.