Issue

Some users are running into overflow error when creating a total sum of `[Epic].[Budget]` field in Atlassian Analytics due to INT field type limitation of -2147483648 to 2147483647.

While it's possible to CAST the field AS BIGINT as a workaround in the SQL editor, it's not an option in the visual editor. It's also possible to add a custom column in AA schema, but users need advanced permissions to manage it.

It would help, if the field type was Long or BIGINT and synced to EI/AA as the larger number type, then users are unlikely to run into the limit.

Feature request

Please change the source field type and the EI schema type to Long/BIGINT, so that it can be summed in the visual editor of Atlassian Analytics.

Workarounds

SQL editor

Once the visual query in Atlassian Analytics is complete and no further modifications are expected, replace the SUM of Budget in the SELECT query with the following:

SUM(CAST([Epic].[Budget] as BIGINT)) AS [Total sum of Budget]

This will convert the field type to a larger BIGINT type which has limits of -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807.

Once the visual query is modified in the SQL editor, it can no longer be edited in the visual editor.

Custom Schema Additional Column

It's also possible to add a custom column to the table in Schema Administration to use in the query builder. 

For example:

1. Go to Data → Jira Align Enterprise Insights Datasource → Schema  
2. Expand Epics table and click 'Add Custom Column'
3. Give it a name and Query:

   CAST(Budget AS BIGINT)

4. Untick 'Aggregated' and select Total Sum for 'Default aggregation'
5. Adjust the rest of the details as needed and click Save

This will allow using the newly created column in the visual editor without running into the same overflow error.