Documentation for non-current version Vivid Trace 1.2.
See documentation for the current release Vivid Trace 1.4

Vivid Trace 1.2 Specifications

System Requirements

Atlassian JIRA Server, starting from JIRA version 5.1. JIRA Requirements also apply directly to Vivid Trace, including supported browsers and devices.

The only additional requirement made by Vivid Trace is that the Issue Linking feature and/or the Sub-tasks feature are enabled in JIRA. These features have been enabled by default in new JIRA installations since JIRA version 5.1.

JIRA Edition Availability

Vivid Trace is available for JIRA Server and JIRA Data Center. It is not currently available for JIRA Cloud.

Compatibility with 3rd-Party Add-Ons

Vivid Trace supports the issue types, sub-task types, and issue link types packaged with JIRA, those packaged with the Atlassian JIRA Agile and Zephyr for JIRA add-ons, and those created manually by JIRA administrators using the administration pages bundled with JIRA.

Localizations

The add-on includes complete localizations for these languages: English (default), German (Deutsch) locale de_DE, Japanese (日本語) locale ja_JP.

Product documentation is available in: English.

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

Design Commitment

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.

While users of older, supported web browsers such as Microsoft Internet Explorer 8 might experience visual degradations due to historic incompatibilities, interactive functionality with Vivid Trace is nonetheless warranted as complete.

Universal Accessibility

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.

If you have concerns, or suggestions for improving Vivid Trace to better suit your needs, please tell us