When exporting a kanban we should export the kanban's main field

[FelixMalfait]

When we do a CSV export we only export visible fields on the current (debatable choice, maybe we would eventually ask for a preference/confirmation?).

When you export from a kanban view, the field that was used to build the kanban columns is not considered as part of the export. This is not desirable as this is usually the most important field. Right now the trick is to come back to a list view and export the data from there.

Steps to reproduce:

• Go to opportunities Kanban
• Click on Options > Export
• You'll that "stage" field isn't in the export

[greptile-apps]

To include the kanban field in the CSV export, follow these steps:

1. Locate the Kanban Field Metadata: Ensure you have access to the kanban field metadata. This is likely defined in a configuration file or within the kanban view component.

2. Modify Export Logic: Update the export logic to include the kanban field. This logic is likely found in the file responsible for handling CSV exports.

3. Update Export Function: In the export function, ensure the kanban field is added to the list of fields to be exported. This may involve modifying the function that gathers the fields for export.

4. Example Code:

// Assuming the export function is in `export.js`
function exportToCSV(data, fields) {
  // Add kanban field to fields if not already included
  if (!fields.includes('kanbanField')) {
    fields.push('kanbanField');
  }
  // Proceed with export logic
  // ...
}

5. Verify Changes: Ensure the kanban field is correctly included in the exported CSV by testing the export functionality from the kanban view.

References

_{Edit Issue Bot Settings}