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

Handle asana subtask #37

Open
zippeurfou opened this issue Jun 12, 2015 · 4 comments
Open

Handle asana subtask #37

zippeurfou opened this issue Jun 12, 2015 · 4 comments

Comments

@zippeurfou
Copy link

Make Asana subtask as task list on github.

@marcboscher
Copy link
Owner

We've been thinking about this one. Can you say more about your use case?

Some ideas we have:

  • Only subtask titles (how would you expect to deal with subtask fields like description, tags, etc)
  • One way only? E.g. read only in github
  • Create an issue for each subtask

Otherwise, in asana you can use markdown to build a task list in the task description and that will produce the expected task list in GitHub. Except you're not leverage subtasks in asana.

@zippeurfou
Copy link
Author

I would do it in two phases. First a quick solution to actually not loose anything. Secondly, a more elaborated solution that treat everything.

  1. Solution 1 which just generate the markdown on the github
  2. Create an issue for each subtasks and have a generic name for the issue: i.e. < Main task > => < sub task > and add a label "sub-task" next to it.
    PS: This plugin is really nice. We are very happy with it. We are using it on our server and it runs very well!

@gregoirebois
Copy link

We've been thinking about this one. Can you say more about your use case?

Some ideas we have:

  • Only subtask titles (how would you expect to deal with subtask fields like description, tags, etc)
  • One way only? E.g. read only in github
  • Create an issue for each subtask

Otherwise, in asana you can use markdown to build a task list in the task description and that will produce the expected task list in GitHub. Except you're not leverage subtasks in asana.

[--- Linked with ASANA.com using Unito.io
#commenter Marc
---[aa]

1 similar comment
@gregoirebois
Copy link

We've been thinking about this one. Can you say more about your use case?

Some ideas we have:

  • Only subtask titles (how would you expect to deal with subtask fields like description, tags, etc)
  • One way only? E.g. read only in github
  • Create an issue for each subtask

Otherwise, in asana you can use markdown to build a task list in the task description and that will produce the expected task list in GitHub. Except you're not leverage subtasks in asana.

[--- Linked with ASANA.com using Unito.io
#commenter Marc
---[aa]

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

No branches or pull requests

3 participants