# Jira: Daily Issue Field History

## Description

* Each record represents a snapshot of an issue's selected fields (as specified in the `issue_history_columns` variable + sprint and status by default) on a given day. Each issue will have a record for every day in which it was open and/or being updated. For currently open issues, the latest date will be the current date, and for closed issues, this will be the last time the issue was resolved OR updated in any way (plus a configurable buffer afterward, set to a month by default). Note: this is an incremental model.

## Supported Data Sources

* <img src="https://fivetran.com/integrations/jira/resources/jira.svg" alt="" data-size="line"> Jira

## Columns

| Type    | Name           | Description                                                        |
| ------- | -------------- | ------------------------------------------------------------------ |
| DATE    | date\_day      | Date on which the issue had these field values.                    |
| INTEGER | issue\_id      | Foreign key referencing the ID of the `issue` with these values.   |
| STRING  | status         | The name of the status that an issue has on a given day.           |
| STRING  | status\_id     | The ID of the status that an issue has on a given day.             |
| STRING  | sprint         | The ID of the sprint that an issue is slotted into on a given day. |
| STRING  | summary        |                                                                    |
| STRING  | story\_points  |                                                                    |
| STRING  | components     |                                                                    |
| STRING  | issue\_day\_id | Surrogate key hashed on `date_day` and `issue_id`                  |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://endash-guidance-docs.gitbook.io/cigro-data-templates/data-model-templates/jira-daily-issue-field-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.