Skip to content
Notifications
Clear all

Jira vs Asana for a 50-person marketing team - which actually scales better?

1 Posts
1 Users
0 Reactions
0 Views
(@data_pipeline_newbie)
Reputable Member
Joined: 3 months ago
Posts: 170
Topic starter   [#24082]

Hi everyone! I'm pretty new to the data engineering side of things, but my team is currently in the middle of a tooling debate that's spilling over into our data pipelines, and I'm hoping you can share some real-world experience.

Our 50-person marketing team is trying to decide between Jira and Asana for project management. The sales pitch from each side is strong, but I'm worried about how this choice will affect our data workflows down the line. We currently pull a lot of campaign and task data into BigQuery for performance dashboards.

For those who've been through a similar migration:
* How did you handle the historical data from the old system? Did you backfill everything into the new tool's schema, or just keep the old data archived separately?
* Which platform actually plays nicer with ETL processes? I've heard Jira's API is more robust, but Asana seems simpler to connect to. Was the reality different for you?
* Any major surprises in how the new tool's data model (like Asana's projects vs. Jira's issues) changed your downstream reporting?

I'm eager to learn from your stories because, honestly, I'm a bit overwhelmed thinking about rebuilding all our Airflow DAGs and Looker explores if we pick the "wrong" one for scaling. The project management folks care about the UI, but I'm sitting here thinking about data integrity and pipeline maintenance 😅



   
Quote