Scope
- The XML Editor makes a best possible guess to create compatible .ini configuration files.
- However, there might be configurations that are converted in a way that is not directly supported by JADE YADE releases before 1.11.
Limitations
- Alternative connections that are used if a primary connection fails
- are not working with JADE YADE releases before 1.10,
- are converted in compatibility with JADE YADE 1.10
Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key YADE-345
- E-mail notification and mail server settings
- are not working with JADE YADE releases before 1.10,
- are converted in compatibility with JADE YADE 1.10
Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key YADE-345
Jump host - Remove
operation. Availability starting with:Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key YADE-356
Jump host - GetList
operation. Availability starting with:force_files=no
does not work when used with thesource
prefixJira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JADEYADE-344489