Neon/Vivid Trace Jira add-on — English @ Vivid I18n: VTE-2: JQL function {0}() doesn''t accept the "{1}" parameter, which …

Contribution to this translation requires you to agree with a contributor agreement.

Source string

Key

English

Needs editing

Contributing to this translation requires agreeing to its contributor agreement.

Skip

	Key	English	Actions
	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.
	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}
	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}
	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.

	Key	English	Actions
	vivid.trace.embeddable-trace.caption	Trace:
	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-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	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-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-17-license-invalid	VTE-17: Please contact your Jira administrators to configure ${product.shortname} with a valid license.
	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-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-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-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.
	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.
	vivid.trace.error.vte-3-jql-function-incorrect-function-usage	VTE-3: Incorrect usage of JQL function {0}(): Usage: {1}
	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}
	vivid.trace.export.description	Export this Issue Relation Graph as a file
	vivid.trace.graph-direction.down	Top-down

Loading…

No matching activity found.

Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Java MessageFormat: Chinese (Traditional, Hong Kong), Chinese (Traditional)

Reset

Glossary

English	English
No related strings found in the glossary.

String information

Screenshot context

Key

vivid.trace.error.vte-2-jql-function-unaccepted-function-parameter

Flags

auto-java-messageformat, ignore-long-untranslated

String age

3 years ago

Last updated

10 months ago

Source string age

3 years ago

Translation file

vivid-trace-jira-i18n.properties, string 179