It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Remove comma from numeric field

Please tell me, I can remove the comma automatically inserted in the numeric custom field in Jira. I am using OnDemand and am therefore unable to use some of the obvious solutions found on the net

4 answers

1 accepted

You can't change this in JIRA onDemand as it involves editing some system files.

Deleted user Dec 13, 2017

Hi, just checking in to see any progress as we face the same issue, the number showing in 5,555 for 4-digit with comma; wonder any solution not to use 1000 separator ? 

The number we need is created during data migration, and somehow it cannot be searched in right top corner, either. 

cc @Kathrine Lauritzen  @Jobin_Kuruvilla__Go2Group_  @Nic_Brough__Adaptavist_ @Brant_Schroeder

Deleted user Dec 13, 2017

just wonder how to resolve ',' issue completely in year 2017 or 2018 :-) 

It's not an "issue" - most humans prefer to see the separators!  So, it's not changed.

Deleted user Dec 13, 2017

oh, even though that is driven by 1000 separator ?  :-) I see your point, if we use number for currency, that is perfect, thousand, million

thank you for sharing your thought, Nic. 

Deleted user Dec 13, 2017

1000 with comma can be chosen.JPG

it would be great not to see ',' 

That's excel, nothing to do with Jira

Deleted user Dec 13, 2017

right, that is what we wish for -  to use or not to use ',' :-)

Like brastatter likes this

Thank you though,  and I also got some feedback regarding quick search,  I was told that no way to conduct number quick search, with ',' or without :-)  (not by query line)

How is this the accepted answer? I need to suppress commas, regardless of what anyone says and the logic behind their argument. I can do this with every piece of software I use -- except for this one. Do I need to open a new thread since 'cannot be done' seems to be the order of the day on this one?

For the record, it's not what we have to say here. It is how we say it. Some of you could use a lesson in this little thing called TACT. Of course, now that I have descended into the muck, I'm going to Linkedin Learning now to find that class myself.

Like # people like this

@Nic Brough [Adaptavist] "most humans prefer to see the separators!  So, it's not changed."


What a narrow minded comment. What about numbers that don't have commas, such as product numbers, account numbers and the sort. Having commas changes the functionality of that number. 

No, you're falling into a very narrow mindedview yourself there.

Think about it - product numbers, account numbers and other identifiers like that are not numbers, they are strings that happen to be constrained to  numbers.  If my bank account "number" was ABGORB32 it wouldn't be any better or worse than 71153622. 

If you don't want separators in your fields, then use a text field.  Separators are incredibly useful for humans when handling numbers, and I stand by "most humans prefer to see the separators", because it's inarguably correct.

@Nic_Brough__Adaptavist_ Every other software has a checkbox to enable/disable this option.... but Jira. Including Excel, arguably one of largest numbers software on the planet. 

Bank accounts are ALWAYS numbers so no, they are not strings and no, they do not have commas separators. 

Phone numbers are just numbers. SSN are just numbers, EIN numbers are numbers. Shall I go on? Do YOU want to think about it a bit more?!

Like Andy_Bostian likes this

<sigh> No, they're not numbers, as I've already pointed out. 

Forcing a format that is not universally used is really bad practice. 

Using a text field if you want an integer is a really bad practice:

  • it's useful to be able to order filter results in numeric order
  • it's useful to be able to filter for an integer range (corresponding to a changelist)
  • it's a soft validation check that the correct information is being entered (value must be an integer)
  • indexing text fields versus integer fields impacts performance

The international consensus also shuns the comma or period:
"Numbers consisting of long sequences of digits can be made more readable by separating them into groups, preferably groups of three, separated by a small space. For this reason, ISO 31-0 specifies that such groups of digits should never be separated by a comma or point, as these are reserved for use as the decimal sign"


But yeah, after 3 years of browsing this forums, I would be genuinely surprised not to find Nic here telling people how outrageous and entitled it is to have requirements that exceed current offering...

Like # people like this
0 votes
Joe_Pitt Community Leader Jun 06, 2018

People, @Nic_Brough__Adaptavist_ doesn't work for Atlassian. He is just saying how it is implemented. And I agree, humans like to see the separators. It makes it easy to see the magnitude. 

Hey people, who said he did? Glad you agree and are completely at odds with how every other software on the planet works and how numbers work. 

Like # people like this

The only alternative I have found is that you need to use a Text Field.

You may be able to add custom Triggers, Conditions and/or Validators to your flow for ensuring the number format is correct in your project's Workflow. Quite a bit of work for a simple number field but that's what I would do if you need a certain level of accuracy.

Can we all just agree that the number field should not have comma separators, and Jira should either add the comma as an option or create a currency field (hopefully one that supports more than just the western standard: $1,000,000.00.

Example currency format in France: 1 000 000,00

  • Comma is used instead of a decimal
  • Spaces are used instead of commas for decimal numbers

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you