Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Before you can start using the Mapit plugin, you need to set up some custom fields to store location information for issues.
1. Geographic coordinate system
Select which geographic coordinate system you would like to use for storing the issue position. Supported formats are latitude/longitude (default) and UTM.
Info |
---|
You can change the geographic coordinate system at any point, but please note that issues created with one system will not show on the map after the change. So if an issue has been created and stored UTM information, it will not be able to show in the map if setting is chaged to lat/long. |
2. Creating custom fields
Mapit makes use of 3 different custom fields to store location information. If you don't have these fields already, you need to create them:
Panel |
---|
If you have opted for UTM Geographic coordinate system, use only one field holding the value with the position. |
Panel |
---|
If you have opted for UTM Geographic coordinate system, you need 2 different custom fields.
|
Please refer to the following Atlassian documentation page for more information on how to create custom fields:
Anchor | ||||
---|---|---|---|---|
|
3. Placing custom fields on screens
The custom fields (latitude position, longitude position and address or UTM position and adress) need to be placed on issue screens in order for them to be visible to your users. If creating custom fields from the admin section, you will be asked to do this in the last step of the creation process, but you can also do this manually. Please refer to the following Atlassian documentation for your preferred method:
4. Associate custom fields with Mapit parameters
Once the custom fields have been created, they need to be mapped to the correct Mapit parameters. Go to the add-ons administration section of your JIRA instance, and choose "General configuration" in the Mapit Configuration section.
Panel |
---|
Only custom fields of supported types will be listed in the drop-downs. |
Note |
---|
All custom fields must be of the supported types:
Remember that used custom fields must be searchable. Learn more about configuring custom fields and Search templates. |