Wana Asana用户在任务下的注释中引用另一个Asana用户，其中带有“@”引用+用户名 ，Asana将其替换为用户名作为超链接，指向Asana中的用户任务页面。 只要从Asana中查看它就可以了，因为只有用户名在注释中可见。 但是当外部系统通过Asana API查询任务和故事时， 作为JSON返回的内容只包含超链接而不是用户名 。 外部系统无法知道注释中引用的（带有@）用户名。 超链接在URL中有一些ID，但ID不是用户，任务，工作空间或项目，我们可以从中间接或直接获取用户名。 因此，评论变得模糊，使得帖子/任务历史混乱。
问题：Asana是否已经意识到这个问题并解决了同样的问题？ 有什么建议可以克服同样的问题吗？
建议：如果Asana可以发送用户名或用户ID，并且某种方式表明它是对用户的@reference，那将更有意义。
Whan an Asana user refers to another Asana user with '@' reference + user name in a comment under a task, Asana replaces it with user name as hyperlink referring to the user's tasks page in Asana. This is fine as long as it is viewed from within Asana, as only the user name is visible in the comment. But when an external system queries the task and stories through Asana API, the content returned as JSON has only the hyperlink instead and not the user name. The external system has no way of knowing the referred (with @) user name in the comment. The hyperlink has some ID in the URL, but the ID is none of user, task, workspace or project from which we will be able to get the user name indirectly or directly. Hence the comment becomes obscure making the post/task history confusing.
Question: Is Asana already aware of the issue and addressing the same? Are there any recommendations to overcome the same?
Suggestions: If Asana can send username or userid along with it and some way to indicate it is an @reference to a user, it will make more sense.
最满意答案
有关Asana中用户链接表示的详细说明，以及通过评论的超文本版本获取实际名称（可能仍然不受支持）的方式，请参阅故事中用户的超链接提及 。
另一种解决方案是将该人员的“Assigned to Me”项目 URL ID映射到API中使用的Asana用户ID。 这需要维护，因为额外的用户被添加到Asana。
Refer to Hyperlink Mentions of Users in Stories for a detailed explanation of the representation of user links in Asana along with a (possibly still unsupported) manner to get an actual name via the hypertext version of a comment.
Another solution is to map the that person's "Assigned to Me" project URL ID to the Asana user ID that is used in the API. This requires maintenance as additional users are added to Asana.
更多推荐
发布评论