This item has shipped. I will update the status. Sorry for the confusion.

Was there a new timeframe for when this item is expected to release?

I would also like to add to this: for the same reason David mentioned, could preferred name be one of the required fields in settings? Without requiring this in NXT, we still have to go to DBV to correct them often.

We are currently working on this item and expect a release in Q2.

I know I've already added a comment, but I feel that it warrants a second one. This feature seems fairly necessary for the following example: let's say I have a donor named "Mark Anthony Smith" but they go by "Tony Smith."

So, in my database I'd have "Mark" in First Name, "Anthony" in Middle, "Tony" in Preferred, and "Smith" in Last.

For the purposes of doing donor research or data enrichment searches I want to have Tony's full name in the system. For the purposes of sending correspondence to him, though, I want to have a consistent way of pulling the preferred name in Addressee/Salutation settings.  For the very reason that my org has a number of people who have names like this I've set it so that the "Preferred Name" field (ie "Nickname") as a required field in database view and ask those who create new individuals to enter the appropriate value there, even if it's just the same as First Name.

This would be very beneficial to us as we have a lot of foreign students that have a preferred name/nickname which they prefer to be addressed as.   In NXT i have to add the constituent and then save it to go back into it to add the nickname/preferred name.  Please can this be changed

I voted for this exact same reason; my org's addressee and salutations use the nickname/preferred name field exclusively, so it's a significant hassle to not have this field available in the create new constituent window.