[ Upcoming ] New V1 Asana URL format in the browser

Summary

Asana is updating its URL format in the web browser to improve readability and performance by adding human-readable segments to URLs.

**Current URL Format (V0)**
https://app.asana.com/0/1206043162733419/12058909747493732

**New URL Format (V1)**
https://app.asana.com/1/15793206719/project/1206043162733419/task/12058909747493732

All links in the browser will change once this is fully released, but the previous URL format (V0) will still be supported indefinitely.

This has no bearing on API endpoint formats: all API endpoints and their URIs will not be changed.

Who is affected

Apps that parse Asana URLs may need to update their logic to account for the new format.

Our upcoming release will include the following pages, with more pages potentially migrating to this format in the future:

  • Tasks in a project
  • Task stories (comments)
  • Projects / project views
  • Inbox
  • Project create dialog (static)
  • Project template gallery (static)

See the table below for more detail.

Change details

New V1 URL format

Logic to parse a IDs from a URL will need to be updated to accommodate the new URL format:

**Current Task URL (V0)**
https://app.asana.com/0/<project_id>/<task_id>

**New Task URL (V1)**
https://app.asana.com/1/<workspace_id>/project/<project_id>/task/<task_id>

**General V1 format**
https://app.asana.com/<url_format_version>/<workspace_id>/<object_name>/<object_id>/<subobject_name>/<subobject_id>

This new format has three defining characteristics:

  1. All object IDs will be preceded by an identifier segment / object type name, e.g. /project/123
  2. <workspace_id> will be added in V1 URLs as a second parameter (after <url_format_version>/ )
  3. Some URLs don’t have any IDs at all and multiple static segments can exist in the sequence, e.g. /create-project/template-gallery or /project/123/timeline

Here are the specific objects we will change in the upcoming release. Others will follow this format in the future (goals, portfolios, etc), but will not be changed in the upcoming release.

Object New URL format
Project /project/<project_id>
Task in a project /project/<project_id>/task/<task_id>
Task without a project* /1/<workspace_gid>/task/<task_gid>
Task comment in a project /project/<project_id>/task/<task_id>/comment/<comment_id>
Project with named view /project/<project_id>/<view_name>
Project with custom view /project/<project_id>/view/<view_id>
Project with an LLM Question /project/<project_id>/llmAskQuestion/<llmAskQuestion_id>
Project with an LLM Thread /project/<project_id>/llmAgentThread/<llmAgentThread_id>
Home /home
Task in Home /home/task/<task_id>
Inbox /inbox/<domainUser_id>
Inbox with an item and story /inbox/<domainUser_id>/item/<item_id>/story/<story_id>
Create project dialog /create-project
Project template gallery /create-project/template-gallery

Focus mode / Full screen view for tasks
Users may view a task in “focus” or full screen mode. In the current format (V0), these URLS have a /f at the end of the URL path. This will change to a query parameter ?focus=true in the new format (V1).

https://app.asana.com/1/15793206719/project/1206043162733419/task/12058909747493732?focus=true

Screenshot 2025-01-09 at 2.18.28 PM

Returning V1 URLs in the Asana API

Asana objects fetched via the API will reflect this new pattern in their permalink_url field.

GET /project/12345?&opt_fields=permalink_url,name,resource_type,gid

{
  "data": {
    "gid": "12345",
    "resource_type": "project",
    "name": "Winter Campaign Launch",
    "permalink_url": "https://app.asana.com/1/9876543/project/12345" <<<<<
  }
}

Previous URL format will continue to be supported

All existing URLs will still continue to be supported. There are no breaking changes for apps which store or create URLs in the old format. Old links will automatically “redirect” to the new URL structure.

Timeline

  • Feb 27th 2025 - Gradual rollout will start for the objects described in this post and will continue for ~2 weeks
  • Others will likely follow this format in the future (goals, portfolios, etc), but no change is currently planned for those pages.
  • There is no plan to remove support for links using the existing V0 structure.

Questions

Thank you for your understanding as we continue to improve the Asana web app’s URL structure and overall platform performance. Please reply with questions or let us know how we can support you through this transition.

Edit 1: Add mention of focus mode
Edit 2: Adding workspace_id as a key characteristic of V1 URLs
Edit 3: Updated Timeline details

13 Likes

Thanks for the detailed post, @John_Baldo.

Would it be correct to say there’s actually a third defining characteristic of V1:

  • <workspace_id> will be added in V1 URLs (after <url_format_version>/) whereas it is not present in V0 URLs

It seems that way from your post, but it’s not 100% clear. If it is, maybe consider adding that as point #3?

Thanks,

Larry

2 Likes

To be clear, after this rollout, will new links that are created with the “V0” method still work properly too (e.g., will they also be redirected if they are still being created)?

@lpb - Thanks, I think that’s a good point. Made the addition.

@FreshyJon - Yes, a properly formatted V0 link will still work. You may also continue to see V0 links from Asana for objects that aren’t listed in this table (goals, portfolios, etc). So not breaking and also not completely going away. Hope that clarifies.

2 Likes

@John_Baldo Thank you so much for writing this post in such technical detail. Parsing URLs is a major feature / user experience in my Asana application, so I’m thankful for this notice. The new format makes so much more sense. Very exciting!

1 Like

Appreciate the extra work to ensure v0 remains backwards compatible.

2 Likes

Welcome, @Robin_Dutta,

You replied to me, but I suspect you meant to reply to @John_Baldo.

Thanks,

Larry

This is nice and all, but it seems like a distinction without a difference. What about a human readable url or built in URL shortener so we can share ticket links with some context in it?
I would love to see something like

https://app.asana.com/Company/ProjectName/TaskTitle

or better yet a bit.ly like urls shortener with customizable back-half

asana.ly/UniqueTaskTitle

Oops, reposted and deleted wrong one.

1 Like

Thanks for the feedback, @Robin_Dutta. I’ll pass that along.

Just chiming in here to say that I believe I have Asana2Go ready for these changes and will publish a new version in time to be ready for the first updates in about two weeks, thanks to the good documentation here.

Thanks,

Larry

2 Likes

We’ve added one more update to the table in the original post above: task URLs without a project (at least before page load). Specifically, URL formats like https://app.asana.com/0/0/<task_gid> will now appear as https://app.asana.com/1/<workspace_gid>/task/<task_gid> in the new format.

Feel free to continue this thread with any questions or feedback!

Enjoy your weekend, everyone!

2 Likes

@Andrew-asana, Could you explain under what circumstances a user would see this URL in the Asana UI? I tried several things in v0 and it seems to always redirect such that the second 0 becomes a project or my tasks gid. And I can’t do a quick create of a task w/o an assignee or project which was another thing I tried to get to that format of URL.

The reason for my question: I’m trying to support in Asana2Go URLs for tasks but I don’t think this was one that mattered in v0, and I’m curious if it will be used in v1 where it wasn’t in v0?

Thanks,

Larry

@lpb One v0 place I know of is when you right-click a task in a project list view and choose “Copy task link”, you’ll get the https://app.asana.com/0/0/<task_gid> format.

Right, I did test that but I think that gets redirected (or whatever the proper technical term is) to a different URL generally, so I could never get that form of URL to persist, unless I’m missing something.

Thanks,

Larry

Yeah, I suspect that’s what Andrew meant by

What’s interesting is that a URL like that used to, by my recollection, display in a window with just that task by itself, no other elements of the Asana UI present; but now it seems Asana displays the task in its project context (and chooses one of its projects if it’s multi-homed). So maybe that task-only view is gone now?

2 Likes

I may have incorrectly posted this on the Ambassador Forum, so I’m posting here as well:
I have a client experiencing an issue that I’m wondering if it’s related to this update. When trying to utilize the widget in the Figma integration, it is saying that the project URL is invalid:

I was following the instructions in both the Asana Guide and the Figma guide:

Which both state to “copy the project URL” and then paste that into the Figma widget. But every time we did that, it just said the URL was incorrect (Figma message), but gave no explanation as to what was incorrect. And it was strange - I tested it with a portfolio link, and it worked… but an individual project would not.

Is this a bug to report? Is it expected behavior? Will all integrations like this be affected?
Thanks!

1 Like

Hey @Kelsea_Lopez, thank you for reporting this! I wanted to let you know that this issue has been flagged to Figma’s engineering team, and they are looking into it. We appreciate your patience while they investigate, and we’ll update you as soon as we have more information.

Best,

Andrew

3 Likes

Hi @Kelsea_Lopez, the issue has been fixed! The team mentioned that if the updates didn’t appear automatically, please right-click the widget, select Widget, then Update to latest version.

3 Likes

@John_Baldo Hi. We’ve seen V1 URLs in our workspace for a few days and now they seem to have reverted back to V0 URLs. Was there a rollback of this feature or perhaps change of timelines/plans?

2 Likes