Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Act on the behalf of another user for simple Asana actions #101

Open
drzraf opened this issue Feb 4, 2021 · 2 comments
Open

Act on the behalf of another user for simple Asana actions #101

drzraf opened this issue Feb 4, 2021 · 2 comments

Comments

@drzraf
Copy link

drzraf commented Feb 4, 2021

As you know, these Ruby bindings are used by GitLab which parse commit message:

  • to add a comment
  • or close an Asana task

It works well on overall but with one particular drawback: This two actions are realized on the behalf of the user registering the GitLab integration what often makes no sense: If I just setup the integration using my Asana account, all comments and tasks (or likes done on a completed tasks) coming from GitLab commits are authored by me and (with my icon) what is misleading.

(It would be easy to immediately throw the problem to GitLab, but it's not realistic to expect one to configure one token/access per commiter. Some commiters may not even exist in Asana.)

I'm not sure if it's something the core API could solve but I thought this repository could be a nice place to discuss and identify the right component to modify in order to resolve / workaround the problem.

@drzraf drzraf changed the title Act on the behalf of another user for simple Asana action Act on the behalf of another user for simple Asana actions Feb 4, 2021
@rossgrambo-zz
Copy link
Contributor

This is definitely something we're aware of. What we currently recommend users do is create a Bot account within Asana, and then auth the integration with that bot.

We're building out functionality right now that gives Apps better surface area to display things, so they don't have to rely on the user's access token. You can see some of this functionality on our landing page https://asana.com/developers.

Until then, I don't think there's a way to fix this for now. Until we promote apps to be first-class citizens and have their own tokens, I think we're stuck with using the token and the access that the user provides.

@drzraf
Copy link
Author

drzraf commented Apr 20, 2023

up

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants