What are the Jira Mappable fields?

[Lawrence Guy]

HI I am in the process of integrating Jira with Copado for a bi-directional sync. However, I would like to get an idea of which fields are mappable, and which are not. I have found that There is a limitation around look up fields. Besides these, does anyone know how I can find a full list of Jira fields that can be mapped?

[Kai Krause]

Hi and Welcome.

Here are some key points to consider regarding mappable fields and how to find a full list of Jira fields that can be mapped:

Mappable Fields

1. Standard Fields: Most standard fields in Jira, such as Summary, Description, Priority, and Status, are typically mappable.
2. Custom Fields: Custom fields can also be mapped, but you need to ensure that the field types are compatible between Jira and Copado.
3. User Fields: Fields that reference users (like Assignee and Reporter) can usually be mapped, but you may need to ensure that user accounts are synchronized between both systems.

Non-Mappable Fields

1. Lookup Fields: As you mentioned, lookup fields (fields that reference other records) often have limitations and may not be mappable.
2. System Fields: Certain system fields that are managed by Jira (like Created Date, Updated Date) may not be mappable.
3. Field Types: Some field types may not have a direct equivalent in Copado, which can limit mapping options.
   
   
   

4. To find a comprehensive list of Jira fields that can be mapped, you can follow these steps:

   1. Jira API: Use the Jira REST API to retrieve a list of fields. You can access the fields endpoint:

      GET /rest/api/2/field
      

      This will return a list of all fields in your Jira instance, including custom fields.
      
      BR
      Kai