Form field with currency formatting

[klevenick2]

I am building a form for the intake of PO requests using JSM and a Finance Template. We have a field for the PO amount, and it's linked to a custom field setup as a number field with currency formatting. However, on the field itself, I can only input numbers, with no commas allowed. For PO amounts, these are helpful for making sure the input is accurate. Is there any way to allow for commas in these fields?

When you don't have a comma:

When you do have a comma:

[Trudy Claspill · Accepted solution]

Hello @klevenick2 

Welcome to the Atlassian community.

Entering commas into number fields in JSM forms is not currently supported. There is a change request to which you can add your vote for this.

https://jira.atlassian.com/browse/JSDCLOUD-13185

[klevenick2]

Thank you, added!

[Monika Ambrozowicz_Seibert_]

Hi @klevenick2, as Trudy explained, for now Jira's number field doesn't support comma-formatted input. 

If you're open to a Marketplace app, Awesome Custom Fields includes a field type called Price Tag specifically designed for currency and price inputs. It handles currency formatting in a way that's more aligned with how finance teams think about amounts — including proper display formatting. Full disclosure, I'm affiliated with the team behind the app.

You'd replace the native number field on your PO request form with the Price Tag field, which is available in JSM portals and request forms. In addition, you can make it bold and colorful :) 

If you want to explore it, there's a free trial available on the Marketplace listing. Let me know if you have any questions, I'd be happy to help. 

[Olha Yevdokymova_SaaSJet]

Hi @klevenick2 

For Jira/JSM number fields, this is expected behavior. Even if the custom field is formatted as currency for display, the input itself is still treated as a numeric field, so Jira usually expects a plain number value like 10000 rather than 10,000.

That can definitely be frustrating for PO intake, because commas make larger amounts much easier to review and reduce the chance of someone entering the wrong value.

A few options you can consider:

1. Use help text or field description

   Add a short instruction near the field, for example:
   “Enter numbers only, without commas. Example: 10000.”

   This keeps the value compatible with the Jira number/currency field, but it does not improve the typing experience much.

2. Use a text field for the user-facing PO amount

   If readability is more important at the intake step, you could collect the amount in a text field and allow a format like 10,000.00. The downside is that it will not behave like a true number field for reporting, calculations, or sorting unless you also normalize it into another field.

3. Use a form layer with validation

   Another approach you might consider is using Smart Forms for Jira, developed by my team. In Smart Forms, you can create a PO request form with a single-line text field or number field for the PO amount and apply regex validation to control the format users can enter, for example allowing values like 1,000, 10,000.50, or 100000.

   For finance intake, this can be useful because the form can guide users with validation messages, required fields, help text, attachments, and conditional logic before the request is submitted.

   If you still need the Jira custom number field for reporting, I would usually keep a clean numeric Jira field as the system/reporting field and use the formatted form/text value as the user-friendly input or supporting context.

So, for the native JSM number field specifically, commas are not be accepted directly in the input.