You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi guys, just raising this issue that we've found out.
When we've created our portal, no issues like this have occurred. It seems that this was a new issue. Now, months have passed, Commas started to appear within our Mobile Number fields. We've researched it and we found out that to be able to eliminate the commas, we should recreate the fields and change the type to text. But at this time, we can't afford to modify the fields because our portal is live and ongoing in production. Are there any ways to solve this issue? See screenshot below for reference. Thank you in advance.
unfortunately no solution but I remember a discussion on this the day before:
The idea was to involve a text field - as a workaround.
You could probably use Automation (which is included in your Jira Cloud instance with no additional cost) to make advantage of it.
I would recommend the following actions -
1) Please see Atlassian post (NOTE - this not supported by them as stated in the link. It is a conduct at your own risk type of suggestion.) https://confluence.atlassian.com/jirakb/remove-commas-for-values-held-in-number-field-custom-field-type-646250931.html
2) If this issue just started to happen in your env, then you should submit a formal support request with Alassian support.
From my experience, if the custom field is a "Number data type", it will always insert commas in the value as entered.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Hello good day! Thank you for your response.
For the action number 1, is that solution available for Jira Cloud? I believe that formula is only available to Jira Server.
We've implemented this one a few months ago, and there are no issues like these. Probably there are some events that happened in their backend. If we're not able to solve this one with the solutions available online, I guess our final option is to submit a formal support request just what you've recommended. Thank you.
Sorry for not mentioning that we are on DC on-prems in my recommendation. If you find my recommendations helped, please click on "Accept Answer" when you can. Please also post your finding after you obtained Atlassian responses from your formal support reuqest.