# Copyright 2021 Vivid Inc. and/or its affiliates.

# TODO Investigate plural rules, Java ResourceBundle.
# TODO Pull from Atlassian Translations those that make sense.

vivid.trace.access.permission.editor=Edit
vivid.trace.access.permission.owner=Owner
vivid.trace.access.permission.viewer=View
vivid.trace.access.principal.everyone=Everyone
vivid.trace.access.principal.everyone.help=Permit everyone, including anonymous users, subject to security settings.
vivid.trace.access.principal.signed-in-users=All logged-in users
vivid.trace.access.principal.signed-in-users.help=Permit all logged-in users, but not anonymous users, subject to security settings.

# REFERENCE https://translations.atlassian.com/dashboard/translate#/0/0/All Groups/ALL/license%20information
vivid.trace.addon-licensing=${product.shortname} license information
# REFERENCE https://translations.atlassian.com/dashboard/translate#/0/0/All Groups/ALL/license%20updated
vivid.trace.addon-licensing.action.updated=License updated.
# REFERENCE https://translations.atlassian.com/dashboard/translate#/0/0/All Groups/ALL/license%20removed
vivid.trace.addon-licensing.action.removed=License removed.
vivid.trace.addon-licensing.description=Here you can confirm current licensing status and manage ${product.shortname} licenses obtained from your supplier. Licenses issued by the Atlassian Marketplace are managed in the Universal Plugin Manager. Licenses from your supplier override licenses issued by the Atlassian Marketplace.
# REFERENCE https://translations.atlassian.com/dashboard/translate#/0/0/All Groups/ALL/admin.license.type
vivid.trace.addon-licensing.details.license-type=License type
# REFERENCE https://translations.atlassian.com/dashboard/translate#/0/0/All Groups/ALL/admin.license.organisation
vivid.trace.addon-licensing.details.organization=Organization
# REFERENCE https://translations.atlassian.com/dashboard/translate#/0/0/All Groups/ALL/admin.license.date.purchased
vivid.trace.addon-licensing.details.purchase-date=Date purchased
# REFERENCE https://translations.atlassian.com/dashboard/translate#/0/0/All Groups/ALL/admin.license.sen
# "Support Entitlement Number" needs to be localised, and the "(SEN)" text must remain as-is in every language because
# customers need to reference that exact string directly within the license body.
vivid.trace.addon-licensing.details.sen=Support Entitlement Number (SEN)
# REFERENCE https://translations.atlassian.com/dashboard/translate#/0/0/All Groups/ALL/setup.license.label
vivid.trace.addon-licensing.details.supplier=Supplier
# REFERENCE https://translations.atlassian.com/dashboard/translate#/0/0/All Groups/ALL/license%20status
vivid.trace.addon-licensing.details.status=Status
vivid.trace.addon-licensing.details.status.active-maintenance=Active maintenance
vivid.trace.addon-licensing.details.status.contrast-dates=This version of ${product.shortname} (Version {0}, Release Date {1}) was released after the maintenance expiry date ({2}).
vivid.trace.addon-licensing.details.status.contrast-users=${product.shortname}''s {0} user license doesn''t meet or exceed Jira''s {1} user license.
vivid.trace.addon-licensing.details.status.invalid-atlassian-marketplace-issued.html=Examine the license in the {1}{0}{2}.
vivid.trace.addon-licensing.details.status.renew-maintenance=This license is not eligible for ${product.shortname} updates published after {0}. If you wish to have access to support and updates after this date, please renew your maintenance.
vivid.trace.addon-licensing.details.status.unlicensed=Unlicensed
vivid.trace.addon-licensing.details.type=${project.name} {0} Users {1}
vivid.trace.addon-licensing.details.type.maintenance=Maintenance (support and updates) expires on {0}
vivid.trace.addon-licensing.license-key=License Key
vivid.trace.addon-licensing.removal.description=Completely removing all licenses from ${product.shortname} will leave it in an unlicensed state, during which ${product.shortname} will not be available for use.
vivid.trace.addon-licensing.removal.header=Remove Supplier-issued license
vivid.trace.addon-licensing.removal.remove-license-button=Remove license
vivid.trace.addon-licensing.removal.title=Remove Supplier-issued license from ${product.shortname}?
vivid.trace.addon-licensing.summary.valid=${product.shortname} is licensed with a valid license.
vivid.trace.addon-licensing.summary.valid-atlassian-marketplace-issued.html=The active license was issued by the Atlassian Marketplace and is {1}managed in the {0}{2}.
vivid.trace.addon-licensing.web-item-label=License

vivid.trace.add-on-configuration.title.description=These add-on settings apply system-wide in this Jira instance. Individual projects can override certain settings. Changes to these settings take effect immediately.
vivid.trace.add-on-configuration.graph-traversal-time-limit=Graph Traversal Time Limit
vivid.trace.add-on-configuration.graph-traversal-time-limit.description.html=Limits the amount of wall-clock time that Jira spends traversing and accumulating information on each issue relation graph query, no matter how idle or busy Jira is. If issue relation graphs take longer than desirable to appear, you can adjust the graph traversal time limit. Reducing the time limit increases the likelihood that issue relation graphs will be truncated, accompanied by warning VTW-15. For further information, see {0}Graph Traversal Time Limit{1}.
vivid.trace.add-on-configuration.issue-count-soft-maximum=Issue Count Soft Maximum
vivid.trace.add-on-configuration.issue-count-soft-maximum.description.html=Limits the number of issues fetched and displayed in issue relation graphs per query. If issue relation graph computations become unacceptably resource intensive, you can adjust the issue count soft maximum as an interim solution. Reducing the soft maximum increases the likelihood that issue relation graphs will be truncated (and accompanied by warning VTW-6), presenting misleading and inconsistent information liable to negatively impact your organization''s decision making processes. Extreme limits, such as 20, might nullify the value of issue relation graphs. For further information, see {0}Issue Count Soft Maximum{1}.

vivid.trace.configure-project.action-button=Configure project…
vivid.trace.configure-project.action-button-title=Configure issue relation graphs for the current project.
vivid.trace.configure-project.issue-link-types-tab=Issue Link Types
vivid.trace.configure-project.manage-issue-types=Manage Jira issue types
vivid.trace.configure-project.manage-custom-fields=Manage custom fields
vivid.trace.configure-project.manage-issue-link-types=Manage issue link types
vivid.trace.configure-project.name=Project Issue Relation Graph Configuration
vivid.trace.configure-project.postamble=Changes made in this project will be immediately visible to all viewers, and do not affect the tracing configurations of other projects.
vivid.trace.configure-project.success=Issue relation graph configuration updated for project "{0}".
vivid.trace.configure-project.summary-description=Control how ${product.shortname} traces are displayed within this project and to whom.
vivid.trace.configure-project.summary-title=Traces

vivid.trace.configure-project.artifact-types-tab=Artifact Types
vivid.trace.configure-project.artifact-types.description.html=This feature allows specific artifact types to be included and irrelevant types to be ignored in traces within the project. Uncheck irrelevant artifact types to trim them from graphs. For further information, see {0}Adjusting Artifact Type Enablements{1}.

vivid.trace.configure-project.issue-context-trace-display-format.description=Traces can be displayed in issue detail views as a panel or as an activity tab. Hide and reveal traces by alternatingly clicking on the panel title or by selecting another activity tab; this personal setting is remembered by your web browser while you continue to work in any project in Jira. When trace panels and activity tabs are hidden, traces are not loaded and will not impact performance.
vivid.trace.configure-project.issue-context-trace-display-format.issuetabpanel=Issue Activity Tab
vivid.trace.configure-project.issue-context-trace-display-format.setting-label=Display format
vivid.trace.configure-project.issue-context-trace-display-format.title=Display Format of Traces in Issue Detail Views
vivid.trace.configure-project.issue-context-trace-display-format.webpanel=Issue Panel

vivid.trace.configure-project.issue-fields.add-row-button=Add row
vivid.trace.configure-project.issue-fields.description.html=This issue field layout determines the information displayed in graphed issues. Customize the layout by selecting from the available issue fields and arranging them in rows. For further information, see {0}Designing Issue Field Layouts{1}.
vivid.trace.configure-project.issue-fields.issue-fields-palette=Available Issue Fields
vivid.trace.configure-project.issue-fields.no-matching-fields=No matching fields.
vivid.trace.configure-project.issue-fields.search-placeholder=Search Fields

vivid.trace.configure-project.issue-link-types.description.html=Issue relation graphs are computed in part by following issue links. The graph configuration determines which issue link types are followed when computing graphs from within this project. Uncheck irrelevant link types to trim them from the graphs. For further information, see {0}Adjusting Issue Link Type Enablements{1}.
vivid.trace.configure-project.issue-link-types.follow-column-heading=Follow

vivid.trace.configure-project.project-contextual-trace-visibility.add-members-title=Add Members
vivid.trace.configure-project.project-contextual-trace-visibility.clear-membership-action=Remove all members
vivid.trace.configure-project.project-contextual-trace-visibility.description=Traces in issue detail views are shown only to viewers of the project who have membership in this list. All other people will not see traces while browsing issues within the project, but they will still be able to trace issues belonging to the project, subject to security settings. This feature can be useful for limiting display of traces to specific users, improving performance for everyone else.
vivid.trace.configure-project.project-contextual-trace-visibility.help=Adjust trace visibility as desired by adding and removing security principals to this visibility list. Setting the list to "All logged-in users" will replace all other entries and make traces visible to any logged-in viewer of issues within the project. Click member entries to manage them or confirm information about them. Changes take effect immediately.
vivid.trace.configure-project.project-contextual-trace-visibility.not-visible-main=Traces are not visible to anyone.
vivid.trace.configure-project.project-contextual-trace-visibility.not-visible-short=Not visible
vivid.trace.configure-project.project-contextual-trace-visibility.not-visible-supplementary=Add members to make traces visible to some or all viewers of issues in the project.
vivid.trace.configure-project.project-contextual-trace-visibility.page-title=Project {0} - ${product.shortname} trace settings
vivid.trace.configure-project.project-contextual-trace-visibility.selector-description=Select members to make traces visible to
vivid.trace.configure-project.project-contextual-trace-visibility.setting-label=Trace visibility
vivid.trace.configure-project.project-contextual-trace-visibility.title=Visibility of Traces in Issue Detail Views

vivid.trace.configure-project.settings.title=Trace settings

vivid.trace.custom-field.description=${product.shortname} custom field.
vivid.trace.custom-field.managed-description=This custom field is managed by ${product.shortname} and cannot be modified.
vivid.trace.custom-field.reindex-message=${product.shortname} Custom Field

vivid.trace.directions.label=Directions
vivid.trace.directions.inward=Inward
vivid.trace.directions.outward=Outward
vivid.trace.directions.parents=Parents
vivid.trace.directions.subtasks=Sub-tasks

vivid.trace.distance.label=Distance
vivid.trace.distance.unlimited=Unlimited

vivid.trace.embeddable-trace.caption=Trace:

vivid.trace.export.description=Export this Issue Relation Graph as a file

vivid.trace.graph-direction.down=Top-down
vivid.trace.graph-direction.label=Graph direction
vivid.trace.graph-direction.left=Leftward
vivid.trace.graph-direction.right=Rightward

vivid.trace.help.show-label=How to use this feature

vivid.trace.issue-field-layout.label=Issue Field Layout

vivid.trace.issue-relation-graph.bulk-change-issues=Bulk change issues
vivid.trace.issue-relation-graph.description=Issue relation graph of issues and their issue link & parent/sub-task relationships. Orphan issues either have no such relations, or their relations are disabled in the project''s issue relation graph configuration.
vivid.trace.issue-relation-graph.display-options-group=Display Options
vivid.trace.issue-relation-graph.list-issues=List issues
vivid.trace.issue-relation-graph.more.description=More operations and settings
vivid.trace.issue-relation-graph.orphan-issues-label=Orphan Issues
vivid.trace.issue-relation-graph.refresh-graph=Refresh graph
vivid.trace.issue-relation-graph.show-relationship-labels=Show relationship labels
vivid.trace.issue-relation-graph.trace-issues=Trace {0} issues
vivid.trace.issue-relation-graph.warning.title=This graph is incomplete, and might be misleading or inconsistent.

vivid.trace.issue-tab-panel.description=Displays the Issue Relation Graph for the current issue.
vivid.trace.issue-tab-panel.name=Trace Issue Panel

# Design note: Textual content must match those in the JQL Reference documentation.
vivid.trace.jql-function.links.name=${product.shortname} links() JQL Function
vivid.trace.jql-function.links.description=Identifies issues reachable from the seed issues by following along issue links, according to parameters.
vivid.trace.jql-function.links.usage=links( [optional PARAMETER] [, more PARAMETERs] ) where PARAMETER is an issue ID or issue key, or one of distance, inclusive, issueLinkType, jql, or projectConfig.
vivid.trace.jql-function.relates-with.name=${product.shortname} relatesWith() JQL Function
vivid.trace.jql-function.relates-with.description=Identifies all issues that relate with, but do not include, the seed issues, according to parameters.
vivid.trace.jql-function.relates-with.usage=relatesWith( PARAMETER [, more PARAMETERs] ) where PARAMETER is an issue ID or issue key, or one of direction, distance, issueLinkType, jql, or projectConfig.
vivid.trace.jql-function.relations.name=${product.shortname} relations() JQL Function
vivid.trace.jql-function.relations.description=Identifies issues that are related to the seed issues by following along issue link and parent/sub-task relationships, according to parameters.
vivid.trace.jql-function.relations.usage=relations( [optional PARAMETER] [, more PARAMETERs] ) where PARAMETER is an issue ID or issue key, or one of direction, distance, inclusive, issueLinkType, jql, or projectConfig.
vivid.trace.jql-function.parents.name=${product.shortname} parents() JQL Function
vivid.trace.jql-function.parents.description=Identifies issues that are parents of the seed issues in terms of parent/sub-task relationships, according to parameters.
vivid.trace.jql-function.parents.usage=parents( PARAMETER [, more PARAMETERs] ) where PARAMETER is an issue ID or issue key, or one of distance, inclusive, issueLinkType, jql, or projectConfig.
vivid.trace.jql-function.sub-tasks.name=${product.shortname} subtasks() JQL Function
vivid.trace.jql-function.sub-tasks.description=Identifies issues that are sub-tasks of the seed issues in terms of parent/sub-task relationships, according to parameters.
vivid.trace.jql-function.sub-tasks.usage=subtasks( PARAMETER [, more PARAMETERs] ) where PARAMETER is an issue ID or issue key, or one of distance, inclusive, issueLinkType, jql, or projectConfig.

vivid.trace.jql-function-parameter.artifact.usage="artifactType = ARTIFACT_TYPE" or "artifactType != ARTIFACT_TYPE" or "artifactType [NOT] IN (ARTIFACT_TYPE [, more ARTIFACT_TYPEs])" where ARTIFACT_TYPE is the name of an artifact type. ARTIFACT_TYPE parameter values that contain JQL punctuation such as spaces must be individually quoted.
vivid.trace.jql-function-parameter.direction.usage="direction = DIRECTION" or "direction != DIRECTION" or "direction [NOT] IN ( DIRECTION [, more DIRECTIONs ] )" where DIRECTION is one of: inward, outward, parents, or subtasks.
vivid.trace.jql-function-parameter.distance.usage="distance = d" where d is an integer 0 <= d <= 2147483647 (a whole number, zero or larger).
vivid.trace.jql-function-parameter.inclusive.usage="inclusive = yes" or "inclusive = true" or "inclusive = no" or "inclusive = false".
vivid.trace.jql-function-parameter.issuelinktype.usage="issueLinkType = ISSUE_LINK_TYPE" or "issueLinkType != ISSUE_LINK_TYPE" or "issueLinkType [NOT] IN (ISSUE_LINK_TYPE [, more ISSUE_LINK_TYPEs])" where ISSUE_LINK_TYPE is the unambiguous ID, name, inward description, or outward description of an issue link type. ISSUE_LINK_TYPE parameter values that contain JQL punctuation such as spaces must be individually quoted.
vivid.trace.jql-function-parameter.jql.usage="jql = JQL_QUERY" where JQL_QUERY is a valid JQL query.
vivid.trace.jql-function-parameter.projectconfig.usage="projectConfig = apply" or "projectConfig = ignore".

vivid.trace.license-about.additional-details=Additional details regarding these and other third party code included in this product, including applicable copyright, legal and licensing notices, are available in the "licenses" directory inside the plugin.
vivid.trace.license-about.terms.html=The use of this product is subject to the terms of the {0}End User License Agreement for ${product.shortname} for Jira{1}, unless otherwise specified therein.

vivid.trace.license-banner.academic-license=Academic license
vivid.trace.license-banner.commercial-license=Commercial license
# REFERENCE https://translations.atlassian.com/dashboard/translate#/0/0/All Groups/ALL/demonstration%20license
vivid.trace.license-banner.demonstration-license=Demonstration license
# REFERENCE https://translations.atlassian.com/dashboard/translate#/0/0/All Groups/ALL/non-profit%20license
vivid.trace.license-banner.non-profit-license=Non-profit license
vivid.trace.license-banner.open-source-license=Open source organization license
# REFERENCE https://en.wikipedia.org/wiki/Traceability#Software_development
vivid.trace.license-banner.title=${product.shortname} ${project.version} Jira Dependency Graph and Traceability for Atlassian Jira
# REFERENCE https://translations.atlassian.com/dashboard/translate#/0/0/All Groups/ALL/trial%20license
vivid.trace.license-banner.trial-license=Trial license

vivid.trace.navigation-bar.recent-traces=Recent Traces
vivid.trace.navigation-bar.touchpoints=Support and Documentation

vivid.trace.project-tab-panel.description=Displays the Issue Relation Graph for the current project.
vivid.trace.project-tab-panel.name=Trace Project Panel

vivid.trace.relations-parameters.label=Relations Parameters

vivid.trace.touchpoint.access-vivid-support=Access {0}Vivid Support{1}

vivid.trace.trace.include-seed-issues=Include seed issues
vivid.trace.trace.label-orphans=Group and label orphan issues
vivid.trace.trace.refresh-workspace.description=Refresh this workspace
vivid.trace.trace.seed-issues=Seed issues
vivid.trace.trace.try-with-longer-timeout={0}Try again{1} with a longer timeout of {2} seconds.

vivid.trace.trace-configuration.add-on-management.title=Trace configurations
vivid.trace.trace-configuration.add-on-management.page-title=${product.shortname} trace configuration management
vivid.trace.trace-configuration.delete-trace-header=Delete trace configuration
vivid.trace.trace-configuration.delete-description=Permanently delete this trace configuration?
vivid.trace.trace-configuration.delete-supplement=The trace configuration will be removed from everyone''s Favorite Traces and permanently deleted from ${product.shortname}. This action is irreversible.
vivid.trace.trace-configuration.duplicate-trace-header=Duplicate trace configuration "{0}"
vivid.trace.trace-configuration.favorite-traces=Favorite traces
vivid.trace.trace-configuration.favorite.acl=Sharing Permissions
vivid.trace.trace-configuration.favorite.description=All trace configurations currently available to you are listed here. Click on an individual trace configuration entry to toggle its favorite status. Favorite trace configurations appear in a side panel within the Trace Studio for quick access.
vivid.trace.trace-configuration.favorite.find-trace-configurations-title=Find trace configurations
vivid.trace.trace-configuration.favorite.manage-trace-configurations=Manage trace configurations
vivid.trace.trace-configuration.favorite.my-effective-access=My Effective Access
vivid.trace.trace-configuration.label=Traces
vivid.trace.trace-configuration.name=Trace configuration
vivid.trace.trace-configuration.name-description=Enter a name for this trace configuration
vivid.trace.trace-configuration.new-trace=New trace
vivid.trace.trace-configuration.new-trace-description=Start a new trace configuration
vivid.trace.trace-configuration.rename-trace-header=Rename trace configuration "{0}"
vivid.trace.trace-configuration.save-trace-header=Save trace configuration
vivid.trace.trace-configuration.save-success=The trace configuration "{0}" has been saved.
vivid.trace.trace-configuration.sharing.description.0=Trace configurations can be shared with people so that they may find and favorite the traces. While a trace configuration can be shared, other people''s trace results might differ from yours depending on their access permissions to the artifacts encountered during the tracing process.
vivid.trace.trace-configuration.sharing.description.1=As a rule, the sharing permissions must always list an owner. If you inadvertently strip yourself of ownership, please ask your Jira administrator to assist with restoring permission.
vivid.trace.trace-configuration.sharing.description.editor={0}Editors{1} may also save their edits back into the trace configuration, overwriting prior settings. Suitable for delegating maintenance duties amongst teammates.
vivid.trace.trace-configuration.sharing.description.owner={0}Owners{1} have full control over the trace configuration, including the ability to modify these sharing permissions, and rename or even delete the trace configuration.
vivid.trace.trace-configuration.sharing.description.viewer={0}Viewers{1} can find, favorite, and run the trace configuration. Permissions are enforced during tracing, so each person''s trace results may differ.
vivid.trace.trace-configuration.sharing.find-traces=Find traces
vivid.trace.trace-configuration.sharing.selector-description=Select members to share this trace configuration with
vivid.trace.trace-configuration.sharing.title=Sharing permissions

vivid.trace.trace-studio.name=Trace Studio
vivid.trace.trace-studio.set-my-jira-home-description=Set my Jira Home to the Trace Studio.

# Design note: Never change the fundamental meaning of message codes that have shipped, current or retired.
vivid.trace.error.vte-1-jql-function-parameter-values-not-found=VTE-1: JQL function {0}() could not find {1}: {2}
vivid.trace.error.vte-2-jql-function-unaccepted-function-parameter=VTE-2: JQL function {0}() doesn''t accept the "{1}" parameter, which is already set to the equivalent of "{2}".
vivid.trace.error.vte-3-jql-function-incorrect-function-usage=VTE-3: Incorrect usage of JQL function {0}(): Usage: {1}
# VTE-4 Retired
# VTE-5 Retired
vivid.trace.error.vte-6-jql-function-jql-query-error=VTE-6: JQL function {0}(): In JQL query "{1}": {2}
vivid.trace.error.vte-7-jql-function-parameter-at-most-once=VTE-7: JQL function {0}(): The "{1}" parameter can be supplied at most once.
vivid.trace.error.vte-8-jql-function-issue-link-type-ambiguous=VTE-8: JQL function {0}(): More than one issue link type matches the text "{1}": {2}
# VTE-9 Refactored to VTW-16
vivid.trace.error.vte-10-jql-function-at-least-one-effective-direction=VTE-10: JQL function {0}(): The "{1}" parameter must specify at least one effective direction.
vivid.trace.error.vte-11-jql-function-integer-out-of-range=VTE-11: JQL function {0}(): The "{1}" parameter must be an integer number between {2} and {3}, inclusive.
vivid.trace.error.vte-12-jql-function-search-exception=VTE-12: JQL function {0}(): Could not get search results for {1}: {2}
vivid.trace.error.vte-13-jql-function-requires-seed-issues=VTE-13: JQL function {0}() requires seed issues, supplied using the "issue" and/or "jql" parameters.
vivid.trace.error.vte-14-jql-function-empty-parameter=VTE-14: JQL function {0}(): The "{1}" parameter cannot be empty. Usage: {2}
vivid.trace.error.vte-15-jql-function-parameter-syntax-error=VTE-15: JQL function {0}(): Syntax error at character {1} of "{2}" parameter. Usage: {3}
vivid.trace.error.vte-16-relations-invalid-custom-field-admin=VTE-16: ${product.shortname} cannot be used while its custom field is damaged or missing. To restore functionality, please ensure the {0}custom field "{1}"{2} is removed if possible, disable then re-enable the {3}${product.shortname} add-on{4} or alternatively restart Jira, and then {5}perform a re-index{6}.
vivid.trace.error.vte-16-relations-invalid-custom-field=VTE-16: ${product.shortname} cannot be used while its custom field is damaged or missing. Please contact your Jira administrators to restore functionality.
vivid.trace.error.vte-17-license-invalid-admin=VTE-17: Please {0}enter a valid license{1} to activate ${product.shortname}.
vivid.trace.error.vte-17-license-invalid-admin-plaintext=VTE-17: Please enter a valid license to activate ${product.shortname}. Encountered license validation errors: {0}
vivid.trace.error.vte-17-license-invalid=VTE-17: Please contact your Jira administrators to configure ${product.shortname} with a valid license.
# VTE-18 Retired
vivid.trace.error.vte-19-internal-error=VTE-19: An internal error occurred. For support, please report the following information to Vivid Support.
vivid.trace.error.vte-19-internal-error.actions={0}Download a support ZIP file{1} of the technical details and send it to your Jira administrator or attach it when you raise a support request at {2}Vivid Support{3}.
vivid.trace.error.vte-20-unknown-object=VTE-20: Either {0} "{1}" doesn''t exist or you don''t have permission to access it.
vivid.trace.error.vte-21-license-format=VTE-21: That license key was malformed and could not be applied. Ensure that the entire ${product.shortname} add-on license key is entered exactly as provided. For assistance, contact your supplier or Vivid Support.
vivid.trace.error.vte-22-license-incompatible-version=VTE-22: License is for an older version of ${product.shortname} and maintenance has expired.
vivid.trace.error.vte-23-license-incompatible-users=VTE-23: License is incompatible with number of users in Jira license.
vivid.trace.error.vte-24-jira-communication-error=VTE-24: Jira could not be contacted.
# VTE-25 Retired
vivid.trace.error.vte-26-authentication-required=VTE-26: This operation can only be performed while authenticated. Please {0}log in{1} and try again.
vivid.trace.error.vte-27-malformed-request=VTE-27: Malformed request: {0}
vivid.trace.error.vte-28-access-denied=VTE-28: Access denied. Please contact your Jira administrators for permission.
# VTE-29 in Vivid Trace for Confluence

vivid.trace.warning.vtw-1-jql-function-issue-linking-deactivated=VTW-1: JQL function {0}() is making use of issue link relationship information while Jira''s Issue Linking feature is deactivated. Results might be incorrect.
vivid.trace.warning.vtw-2-jql-function-sub-tasks-deactivated=VTW-2: JQL function {0}() is making use of parent and sub-task relationship information while Jira''s Sub-tasks feature is deactivated. Results might be incorrect.
# VTW-3 Retired
vivid.trace.warning.vtw-4-jql-function-no-seed-issues-found=VTW-4: JQL function {0}(): No seed issues were found.
vivid.trace.warning.vtw-5-jql-function-issue-link-types-without-direction=VTW-5: JQL function {0}(): Issue link types were set even though the effective directions ({1}) don''t include issue links.
vivid.trace.warning.vtw-6-issue-relation-graph-issue-count-soft-maximum-truncation=VTW-6: Limiting quantity of displayed issues to the Issue Count Soft Maximum of {0}.
vivid.trace.warning.vtw-7-insufficient-permissions-truncation=VTW-7: One or more issues have been omitted due to insufficient browse permissions.
vivid.trace.warning.vtw-8-issue-linking-admin-deactivated=VTW-8: Issue Linking is deactivated and is not available to ${product.shortname}. Either ignore this warning, or activate {0}Issue Linking{1} in Jira System Administration.
vivid.trace.warning.vtw-9-sub-tasks-admin-deactivated=VTW-9: Sub-tasks are deactivated and are not available to ${product.shortname}. Either ignore this warning, or activate {0}Sub-tasks{1} in Jira System Administration.
# VTW-10 Retired
vivid.trace.warning.vtw-11-jql-function-jql-query-warning=VTW-11: JQL function {0}(): In JQL query "{1}": {2}
# VTW-12 NOLOCALIZE
vivid.trace.warning.vtw-13-license-updated-but-invalid=VTW-13: The license was successfully updated, but the license is invalid.
vivid.trace.warning.vtw-14-active-maintenance-nearly-expired=VTW-14: Active maintenance will expire in {1} day(s) on {0}.
vivid.trace.warning.vtw-14-maintenance-expired=VTW-14: Maintenance expired on {0}.
# TODO This comes from Confluence 6.0.1:  Your evaluation license for {0} has expired. Here''s the information you need to continue using {0}
vivid.trace.warning.vtw-14-maintenance-recently-expired=VTW-14: Maintenance expired {1} day(s) ago on {0}.
vivid.trace.warning.vtw-15-issue-relation-graph-graph-traversal-time-limit-elapsed=VTW-15: Displaying portion of graph that was discovered within the Graph Traversal Time Limit of {0} seconds.
vivid.trace.warning.vtw-16-jql-function-no-effective-issue-link-types=VTW-16: JQL function {0}(): The effective directions is set to follow issue links ({1}) but there are no effective issue link types.