No more parsing story text! New fields on stories!

English Forum Developers & API
,
22

Did the old name, new name for resource subtype name changed stop working.

23

@Phil_Seeman @Andrew-asana @lpb
Any updates on why old_multi_enum_values, new_multi_enum_values are not returning any values

24

For people using custom fields, and looking for old-new values in stories.

They are only available for text, enum, and number.
They are NOT available for date, people and multi_enum.

Until they add it to the schema.

So, for these, you still need to parse story text!

25

@Joe_Trollo I want to find out when the section has changed. I am able to get the story GID from the webhook payload. When I retrieve the story using rest API, I get the following response:

{
    "data": {
        "gid": "1209337856496191",
        "created_at": "2025-02-06T05:48:52.245Z",
        "created_by": {
            "gid": "1209072868724885",
            "name": "Omer Malik",
            "resource_type": "user"
        },
        "previews": [],
        "resource_type": "story",
        "source": "web",
        "text": "Omer Malik moved this task from \"To do\" to \"Doing\" ",
        "type": "system",
        "resource_subtype": "section_changed",
        "target": {
            "gid": "1209072870388206",
            "name": "Draft project brief",
            "resource_type": "task",
            "resource_subtype": "default_task"
        }
    }
}```

Notice that I am not seeing the old_section/new_section field. Is this still supported?
26

@Phil_Seeman / @Andrew-asana To get wider audience as I can see Joe Trello was last active in Oct 2024.

27

Hi @Omer_Malik,

Yes, FYI Joe Trollo is no linger with Asana.

Here’s the answer I believe, from above:

In other words, you’ll need to include ?opt_fields=old_section, new_section in your API call.

For more info on opt_fields, see the API docs here.