Vivid Trace 2025.1 Specifications
System Requirements
A deployment of Vivid Trace consists of Vivid Trace for Jira installed on Atlassian Jira Data Center, and optionally Vivid Trace for Confluence installed on Atlassian Confluence Data Center.
Atlassian Jira | Any version of Atlassian Jira Data Center that is actively supported by Atlassian and has yet to reach End Of Support status. Vivid Trace is not currently available for Atlassian Cloud. Jira supported platforms also apply to Vivid Trace. Vivid Trace also requires:
|
|---|---|
Atlassian Confluence | Optional. Any version of Atlassian Confluence Data Center that is actively supported by Atlassian and has yet to reach End Of Support status. Vivid Trace is not currently available for Atlassian Cloud. Confluence supported platforms also apply to Vivid Trace. Vivid Trace also requires:
|
Integration
Vivid Trace supports issue types, issue link types, and certain issue fields and custom field types packaged with Jira and some 3rd-party add-ons.
Localizations
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. Within the add-on software, incomplete portions of a localization are filled in according to the host platform's language settings. Vivid's open translation management system welcomes improvements and new language contributions.
| Language | Code | Completeness | Documentation | Support |
|---|---|---|---|---|
| čeština (Czech) | cs | 53 | ||
| Dansk (Danish) | da | 53 | ||
| Español (Spanish) | es | 53 | ||
| English | en | 100 | Available | Available |
| suomi (Finnish) | fi | 53 | ||
| français (French) | fr | 53 | ||
| Deutsch (German) | de | 53 | ||
| italiano (Italian) | it | 53 | ||
| 日本語 (Japanese) | ja | 96 | あります | |
| 한국어 (Korean) | ko | 53 | ||
| Nederlands (Dutch) | nl | 53 | ||
| norsk (Norwegian) | no | 53 | ||
| Polski (Polish) | pl | 53 | ||
| Português (Portuguese) | pt | 53 | ||
| Русский (Russian) | ru | 53 | ||
| svenska (Swedish) | sv | 53 | ||
| Türkçe (Turkish) | tr | 53 | ||
| 中文/中国 (Simplified Chinese) | zh_CN | 53 | ||
| 中文/香港 (Hong Kong Chinese) | zh_HK | 53 | ||
| 中文/台灣 (Taiwan Chinese) | zh_TW | 53 |
Design Commitment
Vivid is committed to being a long-term island of stability and transparency.
Updated and tested versions of Vivid Trace are made available via the Atlassian Marketplace so that Vivid Trace 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 releases of host platforms is dropped when those releases reach end-of-support status.
Due to varying levels of adherence for web standards in supported web browsers, users of supported but older, partially incompatible web browsers might experience functional and visual degradations among other inconveniences.
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.
Contacting Vivid
If you have concerns, or suggestions for improving Vivid Trace to better suit your needs, we welcome your input.