# Jira: Project Enhanced

## Description

* Table of projects enriched with data about its lead, epics, components, and volume and velocity of worktime.

## Supported Data Sources

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

## Columns

| Type     | Name                                            | Description                                                                                           |
| -------- | ----------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| INTEGER  | project\_description                            | Description of the project, if given.                                                                 |
| INTEGER  | project\_id                                     | Unique ID of the project.                                                                             |
| STRING   | project\_key                                    | UI-facing ID of the project. This becomes the default prefix for tasks created within this project.   |
| STRING   | project\_lead\_user\_id                         | Foreign key referencing the ID of the `user` who leads this project.                                  |
| STRING   | project\_name                                   | Title of the project.                                                                                 |
| INTEGER  | project\_category\_id                           | Foreign key referencing the ID of the `project_category` that the project is associated with, if any. |
| INTEGER  | permission\_scheme\_id                          | Foreign key referencing the ID of the `permission_scheme` that the project ascribes to.               |
| DATETIME | \_fivetran\_synced                              |                                                                                                       |
| STRING   | project\_lead\_user\_name                       | User display name of the person leading this project.                                                 |
| INTEGER  | project\_lead\_email                            | Email associated with the project lead.                                                               |
| STRING   | epics                                           | Comma-separated list of epics worked on in this project.                                              |
| STRING   | components                                      | Comma-separated list of components of this project.                                                   |
| INTEGER  | count\_closed\_issues                           | The number of issues closed in this project.                                                          |
| INTEGER  | count\_open\_issues                             | The number of currently un-resolved issues in the project.                                            |
| INTEGER  | count\_open\_assigned\_issues                   | The number of currently open and currently assigned issues in the project.                            |
| DECIMAL  | avg\_close\_time\_days                          | The average time taken to close issues, in days.                                                      |
| DECIMAL  | avg\_assigned\_close\_time\_days                | The average time taken to close issues from their first assignment, in days.                          |
| DECIMAL  | avg\_age\_currently\_open\_days                 | The average age of any currently-open issues.                                                         |
| DECIMAL  | avg\_age\_currently\_open\_assigned\_days       | The average age of any currently-open issues, from their first assignment.                            |
| DECIMAL  | median\_close\_time\_days                       | The median time taken to close issues, in days.                                                       |
| DECIMAL  | median\_age\_currently\_open\_days              | The median age of any currently-open issues.                                                          |
| DECIMAL  | median\_assigned\_close\_time\_days             | The median time taken to close issues from their first assignment, in days.                           |
| DECIMAL  | median\_age\_currently\_open\_assigned\_days    | The median age of any currently-open issues, from their first assignment.                             |
| DECIMAL  | avg\_close\_time\_seconds                       | The average time taken to close issues, in seconds.                                                   |
| DECIMAL  | avg\_assigned\_close\_time\_seconds             | The average time taken to close issues from their first assignment, in seconds.                       |
| DECIMAL  | avg\_age\_currently\_open\_seconds              | The average age of any currently-open issues.                                                         |
| DECIMAL  | avg\_age\_currently\_open\_assigned\_seconds    | The average age of any currently-open issues, from their first assignment.                            |
| DECIMAL  | median\_close\_time\_seconds                    | The median time taken to close issues, in seconds.                                                    |
| DECIMAL  | median\_age\_currently\_open\_seconds           | The median age of any currently-open issues.                                                          |
| DECIMAL  | median\_assigned\_close\_time\_seconds          | The median time taken to close issues from their first assignment, in seconds.                        |
| DECIMAL  | median\_age\_currently\_open\_assigned\_seconds | The median age of any currently-open issues, from their first assignment.                             |


---

# 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-project-enhanced.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.