Dear Atlassian,

We use JIRA to track the progress of contracts worth several millions of pounds. We have a number custom field associated with the JIRA project to hold this value. When we search in JQL within JIRA the number renders correctly and is also nicely readable with the automatic addition of commas.

However, when we use the JIRA macro in Confluence in order to report on the status of these contracts and their costs, the number renders in scientific notation with an exponent (1.7E7). Not only is this inconsistent with the behaviour in a JIRA JQL search, it is highly confusing for the viewers of the reports in Confluence. People viewing the reports are finance people that do not expect to see scientific notation in such a report (see below).

I believe that JIRA is doing some sort of conversion internally into scientific notation for values over 999,999 - which I believe also causes this problem: https://community.atlassian.com/t5/Jira-questions/Why-doesn-t-JIRA-Regular-Expression-Check-validator-work-as/qaq-p/606305

Please ensure consistency by making Confluence and JIRA treat values over 999,999 as proper numbers instead of converting them into exponents! It's terribly confusing in most circumstances.

Best,

Gary

Workaround:

Change the number field type to test field type in Jira/or create a new text field type and use that for adding numbers greater than 6 digits.