Recently when we click on an unformatted number in the task the thousands separator is showing automatically which is annoying since it became annoying to copy the number and remove the comma…
Is there a way apart from making the field text to show only the number without the comma when selecting it.
Ex: unselected:
Selected:
This is the field setting:
@Rabeeh_Adwan - I tested the behavior you’ve described and it’s working the same way for me.
It does seem odd that it suddenly inherits the comma only when clicked.
I’m not sure whether that was an unintentional change from a recent update or whether it’s expected behavior (which would be unfortunate).
@Emily_Roman - would you be able to check on this for us? Is this a bug?
Hi @Bryan_TeamKickstart and @Rabeeh_Adwan, thanks for reaching out and reporting this! I couldn’t find a bug report related to this topic, in this case please contact our support team so they can investigate if this is a bug or expected behaviour: How to contact our Support Team ✉
My workspace is experiencing the same exact issue as @Rabeeh_Adwan where it wasn’t before.
I’ve submitted this as a support request and will report back what they find.
I also just noticed this and it is frustrating. Over a year ago when I started using the numeric field I explicitly tested what happens when I copy/paste out of the field. I don’t mind the comma showing visually, but it’s really frustrating and slows down my work when I need to copy/paste out of Asana and then remove the comma.
So far, the response I got from support was:
-Confirm whether this is specific to a single user or affecting everyone in the org or team (it’s affecting everyone)
-Confirm if the issue is associated with one project or multiple (happening to all projects with this column)
-update browser (didn’t fix)
-clear browser’s cache (didn’t fix)
-try incognito mode (didn’t fix)
-download desktop app (didn’t fix)
Seems a fix was implemented, I just refreshed the board and the separator no longer appears when selecting the field
Can confirm it’s also fixed for us. Good work, team.
Just documenting here that I’ve sent the support team a request to close the ticket as it’s now been fixed. Thanks everyone for rallying the support here and thanks to the Asana devs who fixed this!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.