API Query - Original Task Name

[Ben39]

Is there a way to find the original name of a task that has had its name changed?
Searching the “name_changed” story sub-type, I can see what the task was renamed to but it doesn’t tell me what the name was changed from.

When viewing the task stories in Asana there’s the option to “View Original” that shows me the original task name, so was wondering if there’s a way to extract this through the api.

[lpb]

Welcome, @Ben39,

I believe that, for now, the best you can do is this:

With:

Get stories from a task

. . . if there are two or more name_changed stories, then you can learn what the prior name was before the latest change, but only in that case, and never the very original name.

Thanks,

Larry

[Frederic_Malenfant]

Hi @Ben39 , welcome to the forum.

I think you may have found a bug in the stories.

As described in that thread:

No more parsing story text! New fields on stories!

Hey everyone, we have a new feature to announce! It’s less of a feature, though, and more of a plethora of new fields on stories. A while back, we added the resource_subtype fields in our API to objects like tasks and custom fields. Stories also got this treatment, which some of you may have noticed, but we decided to take it a step further. Instead of just providing the subtype of the story, we now also provide a bunch of extra relevant data as new, structured fields! Here’s an example of a “d…

The story of type “name_changed” should have 2 fields, “old_name” and “new_name”.

I just test it, using the opt_fields parameter, and they are not returned.

In my test, when I ask these 2 values, I get “null” for all story, in the “new_name” attribute, even in the one that is “name_changed”.

And I never get any old_name.

[Phil_Seeman]

cc: @John_Vu @AndrewWong Bug in story API??

[John_Vu]

Hi everyone,

Hmmm I think @Frederic_Malenfant and @Phil_Seeman are right. This looks like a bug. I’ll check in with our API team to make sure. Will update once we have a fix/resolution.