Page Comparison

In the newly created field, the user has to select "Configure" and then click on "Add vLinks Context Config" link. 

There are five options available:

• Issue Link Type (required field) - you can select any of the existing Jira issue link types.

• Synchronise Issue Links - if checked, vLinks will create issue links between issues selected in the vLinks field and the issue where you are using the field. 

• JQL filter - you can insert a desired JQL filter in the textfield. On the right side you can see either a green icon if the filter is valid or a red icon if the filter isn't.

• Set Permission - while checked, all the issues that are corresponding to the JQL filter will be shown, regardless of the users permissions. 

• View Template - you can decide how the template will look. By clicking on the field, a handful of options will show up, like: $issuekey, $summary, $reporter, $assignee, $status, $priority and $customfield_. In the $customfield_ option, you have to insert the correct ID of the desired custom field, for example $customfield_10200. Otherwise, the value of the option will be set to "N/A".

• Sync Parent Links - Sync with Advanced Roadmaps for Jira, more information below.

vLinks is synchronized with Advanced Roadmaps for Jira. In configuration you can enable this option which allows you to use vLinks singlepicker field as a linking tool for Advanced Roadmaps. Enabling this feature gives you three options on how you wish to use it. 

• Sync fields both ways
  Chaging the value of this vLinks field will set value to the Parent Link, and vice versa.
• Update Parent Link
  Changing the value of this vLinks field will update the value of Parent Link. Changing Parent Link won't update this field.
• Read value from Parent Link
  This vLinks field will show value from Parent Link. Changing this field will not update Parent Link.

The issue you are looking for in the vLinks Custom field doesn't exist yet?
Now it is possible to create issues out of the Issue View as inline creation.

You are now able to configure more than one configuration to the individual custom fields. Multiple JQLs and visual options can be configured to show exactly the needed information.

We've added all configuration schemes from every vLinks field in one place. This makes it a lot easier to browse other schemes and copy them from other vLinks fields. You can now select a scheme you would like to take and edit it as you desire. Custom field configuration schemes have never been easier to connect and edit.

Got issue links that you would like to add to vLinks ? No problem. With issue link resync vLinks takes existing issue links and adds them to the existing vLinks custom field. You will have a chance to review changes before applying them.

A screen will appear showing which issues will be affected and you can choose which link to remove or which ones to keep.

"Issue" column represents the issue in which the links are found.

"Found issue links" column represents the issue links that are found within the issue

"Current value" column represents the current value the vLinks field has

"New values" column represents the value the vLinks field will have after the resync is done

Note: vLinks context configurations issue link type has to correspond to the existing issue link for the sync to work as intended.

After the click on the Create new button a panel shows to the right of the custom field. It shows the summary and the issue type of the to-be-created issue.

The configured issue types can be directly chosen through the panel.

In the newly configured vLinks field, choose an issue. After choosing an issue an icon will appear right next to the content. 
By hovering over it an inline dialog containing all the relevant issue information will appear. 

If you only want certain links between issues you can do that by heading over to Issue Linking Scheme under the Issues section in the administration area.

By clicking on the Create new linking scheme you can select which types of links you want to use. After you have created a scheme, you need to associate that scheme with a project. To do this click on the Associate link and select which projects you want the scheme to be applied to.

By using this feature you can make editing linking schemes available to your project admins. This will enable them to edit the linking schemes that are associated with their projects.
If the project doesn't have a custom Issue Linking Scheme, the project admin can create a new one by editing the scheme that is applied (Default Scheme). This will create a new Issue Linking Scheme and associate it with the current project.
To enable this, simply click on the button Enable editing by project admin. 

Editing the linking scheme

Click on the Edit linking scheme button, a new page will be opened. Here you can specify which Issue Link Types you want to use. You will see ones that are already in use on the left, and available link types on the right. You can edit this by simply dragging and dropping the link type.
After you are finished with editing, click the Save button to save your scheme. This will redirect you back to the Issue Links page. 

Now you can display link types in group and also show the direction of the link type. This is applied to each linking scheme created and works with default Jira issue linking.

If you are using the function currentIssue() inside of these functions; customFieldValueFromIssue("", "") or customFieldValueListFromIssue("", "", ""), the currentIssue() mustn't be between quotation marks ( "" ).