The add-on provides several JQL extension to query Version Graph. You All of the JQL operations listed in the below table has two modes of operation. They can either use the Version Graph of the project or they can use semantic versioning. Even if there is only one entry in the Version Graph table of the project they automatically switch to Version Graph Table. If you haven't defined any entry for a project in the Version Graph configuration, they automatically switch to semantic versioning. This is default operation mode. But you can override this and force "semantic versioning" for all of the below queries. In order to force semantic versioning you will need to pass an additional last argument to JQL function, "semantic". For example to force semantic versioning betweenVersions JQL you can use "affectsVersion in betweenVersions("1.0.0", "2.0.0") and it will return all versions using ordering of semantic versions even if you have defined version relationships on the "Version Graph" page.
To all queries you can pass either version id or version name to all JQL clauses. All of this JQL clauses returns list of version and can be combined with other JQL clauses. If you pass version name it is especially important to combine it with a project selection clause because the same version name may belong to different projects. For example several projects may have "1.0.0" version.
...