This would be such a huge improvement. It's done in other fields now so I'm not sure why this hasn't been prioritized for one of the most important native fields. We put all of our requirements in these fields and need to be able to format better for our people to have a better experience. 

Hi community! We use a custom dropdown field called "Work Category" on all of our tasks. Often, subtasks or issues get logged on these tasks. I want them to have the same "Work Category" as the parent task for reporting purposes. I think this can be done with a calculated field but I'm not really su...

Thank you so much! This worked perfectly!

Hi community! I have a calculated field that determines if a request queue issue was submitted via email or the form. (Formula below). It's working correctly but if someone changes the queue topic on the issue, it recalculates and changes the value. I'd like for it to calculate the first time and th...

With request queues, I would like for requests that are emailed in to be assigned to a specific queue topic. Currently, they get randomly assigned which then applies the routing rule from the randomly assigned queue topic. These are usually getting assigned to the wrong topic and wrong people and th...

This worked perfectly! Thanks so much!

I see! I'll try it out and let you know. Thank you for the further explanation. Makes so much more sense.

Thanks Doug! I'm not sure this will work though. I'm looking to calculate the date of the first time that there IS data in the IterationID field. So the first time it goes from blank to not blank.

My plan is to add a calculated field that notes when the iteration ID has a value but I can't determine how to do this so that it adds a timestamp of the first time ANY value is present in that field. Here's where I am and this doesn't work: IF(NOTBLANK{Iteration ID}),IF(ISBLANK({DE:Iteration Assign...