Asana developers or a bug in an update modified one of our custom fields that our company relies heavily upon (affected most of our projects) 75+ and has not been willing to discuss live.
We have reported it in 2 separate tickets 4 days ago (#1069119 and #1069307) and they have made no attempt to truly help us resolve. Per their request I made a video to show them. Responses are in the middle of the night and not helpful at all.
We are extremely frustrated. I used to be a raving fan of Asana but no longer.
Iâm sorry youâre having trouble with this, but Iâm not sure how posting like this is going to help.
I or others on this forum - who are not working for Asana - might be able to advise if youâd share some context, for example by giving details about whatâs happened as the template for the bug report:
Important note: To help us resolve your issue as quickly as possible, please ensure to fill out all the sections below. Do not share any private information such as email addresses or phone numbers - This is a public Forum!
Briefly describe (1-2 sentences) the bug youâre experiencing:
Steps to reproduce:
Browser version:
What version of Asana are you using (Personal, Starter, Advanced, Enterprise, Enterprise+, Premium, Business or legacy Enterprise)?
Now Custom Field says âQualitativeâ which may have been an old custom field we had with 3 options. Previously this said âProject Phaseâ and had 10 options. We used this to make dashboards to capture our time on these Project Phases.
This is from an old screenshot I had for easier Dashboard set up.
Now they look like this as a result of the issue:
I can go in and fix manually, but it will take a very long time as this affects so many projects and underlying tasks.
@Sara_Beth_Watson - Sorry to see youâre having this issue; my 2c - I would wait for Asana to respond (I know youâve already submitted tickets, but I wouldnât respond to them via email, as this will reset the ticket age and push it lower in Asanaâs queue).
I would not start making changes manually to those fields yet, as this seems like a weird db bug where two fields may have gotten merged or mistaken for each other. I would hope that Asana can split this data back up correctly on their end.
Hi @Sara_Beth_Watson , sorry to hear about this but judging from what you describe and your screenshots, Iâm 99% sure that someone in your org has edited this custom fieldâs name and values (options).
To check this, go to edit your field and along the top you will see when it was last modified and by who! Once that is verified you can let them know that you will change it back, as per belowâŠ
You could do this by actually reinstating the field title and the options. The options are tricky though - you will need to map the ones left over now to what they were. Itâs great you have a screenshot so you can make a better guess. If you get it wrong, simply rename to your original options.
Which ever fields were removed though, (such as âQualitativeâ because itâs been striked-out) you can add them back as options and Asana will reinstate them! BUT as long as you type them out EXACTLY as they were, case-sensitive too!
I have done this before and it has worked. If you are in a hurry I suggest you try it out, one option at a time.
If not, wait for support but Iâm not sure they will be able to reinstate the field as it was. Maybe.
And to avoid this from happening again in the future, if you are at least on Business or Advanced tier (or above), you can lock your field from anyone else changing it, by selecting the last checkbox in the fieldâs editor pane!
Hi @Sara_Beth_Watson, thanks for reaching out and sharing more information with us. Sorry to hear you are experiencing this issue!
I have liased with our support team and they will be in touch shortly to help you resolve this. Iâm unfortunately not equipped to give you a tailored answer regarding your specific situation, as I do not have access to see details about the changes in your project. Please bear with us until our team gets back to you via email, we hope this gets resolved soon!
Thanks to everyone who has shared great tips in this thread
@Richard_Sather - you were 100% right! I truly appreciate your detailed instructions. I was able to identify who made the change (by mistake) and then edit the custom field as you instructed and I was about 95% successful. Definitely lesson learned and I locked the field settings so that I am the only one who can edit moving forward. I really appreciate this forumâs support!
Ah, Iâm so glad to hear that, @Sara_Beth_Watson !
95% is certainly a great âdamage-limitationâ score so well done
Just one last thing on locking fields; indeed it is locked from other members making any edits but be aware that any Asana Admin could override and edit anyoneâs locked field.
