Blog Post
Custom tags are supported in Aurora but called custom fields. They are implemented for users, nodes, and discussions and we’re working this quarter to finish them for kb,blog,ideas, events. Custom fields are part of the native graphql APIs so they are easy to set when creating objects without custom endpoints and to query / filter messsge lists or users by. We’ve also fully incorporated them into firehose event feeds and they will be part of the upcoming automaton rules and role assignment in registration.
That's good to hear, and I'm sure that's true of other features we might be using (the basic functionality being called "something else" in Aurora).
We know that we eventually need to move to Aurora, but it's difficult when a bunch of custom functionality needs to be re-implemented.
I assume it's also going to involve Professional Services, since we will have to map data from the "Classic" method to the "Aurora" methods :)
It's an ongoing discussion we're having with our CSM.