I did an Jira Cloud + Asana integration. It turns out that each project can only sync one issue type (e.g. documentation, bug, task, etc.) per board. Therefore if I want to have everything from Jira flow into Asana, I have to build a board per issue type. Then I created a master project and linked all the tasks from the “sub-projects” accordingly.
My issue is that I can’t seem to figure out how to create columns in the master project for the field connections which are reflected in the sub-projects. Is this actually possible? The field connection inputs are available in the task but I can’t actually have it reflected in the column.
@Margs - That is a great workaround for getting all the issue types to pass from Jira to Asana. And I see your problem. I think Asana would need to come up with a way to add the Asana Jira fields (Jira status, Jira priority, Jira labels, Jira Sprint) to our global field library. Then you would be able to add them as columns in your master project.
This still feels a little “hackish” though. I wonder why Asana isn’t just allowing all four issues to pass through to a single project, rendering my proposed function moot?
Just for your future reference, what I ended up doing was creating identical columns in the sub-projects and master-project. Then I created a stupid amount of rules for each sub-project where when the status and/or priority change, they will automatically update the identical columns. It’s a lot of work to make it do what I want it to do.
That’s awesome. I admire your tenacity! I pretty much ended up thinking “I guess this feature is not ready for prime time” and gave up for now. - But that is really good to know if I come back to it before Asana figures this out.
HAHAH! It’s only because I have to get this done Fingers crossed they build out a more robust integration cause it’s pretty useless only importing one issue type at a time in separate boards.
- But that is really good to know if I come back to it before Asana figures this out.
Fingers crossed they build out a more robust integration cause it’s pretty useless only importing one issue type at a time in separate boards.