Users can initiate the CSV data import process into HogoFlow Vantage by first extracting relevant datasets from Jira or alternative task management platforms.
According to 2026 protocols, standard Jira fields—frequently categorized as ‘work items’ within the latest system iterations—are defined by the following parameters:
| Field Name | Description |
|---|---|
| Project | The specific project workspace to which the work item belongs. |
| Work Type | Categorizes the work as a Bug, Story, Task, Epic, or Subtask. |
| Work Key | A unique, permanent identifier for the item (e.g., W-123). |
| Summary | A brief, one-line title that describes the work item. |
| Assignee | The individual currently responsible for completing the work. |
| Priority | Indicates the importance or urgency relative to other items (e.g., Highest to Lowest). |
| Status | The current stage of the item in its workflow (e.g., To Do, In Progress, Done). |
| Created | The system-generated timestamp of when the work item was first entered. |
| Updated | The timestamp reflecting the last time any change was made to the item. |
| Start | The date or time when work is scheduled to begin (often a custom or specific system field). |
| Resolved | The timestamp of when the work item was moved to a “Resolved” or “Done” state. |
| Due date | The scheduled deadline for the work item to be completed. |
| Parent key | The unique identifier of the parent item (e.g., the Epic key for a Story). |
| Parent summary | The title or summary of the parent item associated with the current work. |
| Resolution | A record of how the item was finished (e.g., Fixed, Won’t Do, Duplicate). |
| Team Name | Identifies the specific team assigned to or owning the work item. |
| Link work items | Displays relationships (e.g., “blocks” or “is blocked by”) to other items. |
For Link work items, If you must use the native CSV export, you can merge the multiple “Outward/Inward” columns into one using an Excel formula:
- Export your CSV using Export Excel CSV (current fields) to minimize extra data.
- In a new column, use this formula (assuming your link columns start at column D):
=TEXTJOIN(", ", TRUE, D2:Z2) - This will gather all Issue Keys from the various link columns and put them into one cell, separated by commas.
Select fields by JQL
In Jira, JQL (Jira Query Language) is used exclusively to filter work items, not to select which columns are displayed. To “select” these fields for viewing or export, you must first run a query and then use the Columns interface.
Step 1: Run the JQL Query
Use this query to find all work items (issues) that contain data for the specified fields:
project IS NOT EMPTY AND summary ~ "*" AND status IS NOT EMPTY
Use code with caution.
Note: This broad query ensures you retrieve items with basic standard data.
Step 2: Select the Columns (Fields)
After running your query, follow these steps to display all requested fields:
- Switch to List View: In the top-right of the search results, click the list icon.
- Click Columns: Select the Columns dropdown.
- Search and Check: Type and check the boxes for each of your required fields:
Project,Issue Type,Key,Summary,Assignee,Priority,Status,Created,Updated,Start date,Resolved,Due date,Parent,Resolution,Team, andLink work items.
Pro-Tip for 2026: Saving Views
If you save this JQL search as a Filter, Jira allows you to save the column configuration with it. This ensures that every time you or a teammate opens the filter, all 17 fields are automatically “selected” and visible