Migration to Route custom field

In version 4.3.0, we introduced the new Route custom field, replacing the deprecated Itinerary custom field with enhanced functionality. To fully utilize these improvements, we recommend migrating your Itinerary data to Route. The Itinerary custom field is set to be completely removed in version 4.4.0.

While automatic migration currently isn’t possible due to the introduction of the Route issue type, we kindly ask you to do a manual migration by re-creating the route using the Route custom field.

DEPRECATED

A recent addition to our app is the new custom field called Itinerary. The purpose of this custom field is to allow users to organize Locations from our Location custom field, create the most optimal path between locations within an issue, and generate a link for external navigation applications. For better differentiation between locations of the Location custom field and location in the Itinerary custom field, we denote the Itinerary entries as waypoints.

Setting up the Itinerary Custom field

To utilize the Itinerary custom field, you first need to create it. Click the Administration button in the top right corner. Then select Issues.

Next locate the Custom fields button in the left panel. Look for and click on the Add custom field button on the right side of the page.

This will open a new modal window where you will be able to search for and add a GeoData Location custom field. Make sure you select All in the left panel and type GeoData into the search field. This should show you the correct custom field. If there are more than one results, select GeoData Itinerary custom field and press Next.

Fill in a Name and a Description (optional) for the new custom field and click Next.

On next screen you have the option to select issue types and projects for which this custom field will be available.

By default it is set for all issue types.

You have to select at least one project from the select field. After you select desired projects, you can finish this configuration by clicking on the Create button in the lower right corner.

On the following screen, ensure that you assign the correct screen to the newly added custom field as shown in the image below. For this custom field, all you need to check is Project Management Edit/View Issue Screen.

Once you’ve completed these setup steps, you are now ready to start using the Itinerary custom field!

Using the Itinerary Custom Field#

Working with Itinerary custom field is easy. Once you create an Issue and with some locations, the Itinerary custom field should automatically display a message informing you to adjust your desired route.

This can be accomplished using simple drag & drop functionality of Itinerary custom field.

Once you have ordered the waypoints of your route save the updates and Itinerary custom field will provide you a link pointing to navigation application.

In current release we only support Google Maps navigation.

The Itinerary Custom Field behavior

The Itinerary custom field is fully dependent on the Location custom field. This means that it will automatically synchronize locations from the Location custom field with waypoints in the Itinerary custom field. When you update any editable information in the Location custom field, such as the display name or address, it will not display a message in the Itinerary custom field.

However, if you make changes to information regarding coordinates, like adding new locations or removing locations, which are stored in the Location custom field, a message will appear in the Itinerary custom field. This message will inform you to check and adjust waypoints, if necessary.

If your Location custom field contains only one location, the generated link should open a navigation application from your current position to the destination set as that location.

If your Location custom field contains more than one location, the generated link should open your navigation application with the first waypoint set as the origin point and the last waypoint set as the destination point.