Tara AI 1.0 - The smart and free alternative to Jira.

@akhaliq__ Thank you for being a part of this exciting journey 😊

@rilwan_owolabi1 So as part of this release- no NLP yet! The plan is to assess and really understand the issues teams and individuals face with effort estimation, and how they can be alleviated with some form of "suggestions" around effort based on past performance. We're doing this on a lighter level with the sprint load indicator and plan on doing the same across other parts of the PDLC. I think the key is not to get tied down with having smart features for the sake of being "smart"- we're trying to be thoughtful around how to do suggestions and predictions that actually provide value to teams. We learned that the hard way with an earlier version that was ML-based predictions only (spoiler: it didn't do well). And yes! Can't agree more on the automatic migration. It's on the way! We're thinking through the data models and labelling scenarios around this- the last thing we want to do is have teams manually have to label and structure their data set from Jira. Using it is painful enough.

@georgeallen Thank you! We're working on a few things including integrations and smart indicators. We also need a better way to do effort estimation (usually one of the biggest complaints we've heard from teams from existing PM software). What would you like to see?

@ibamasood I work in a design capacity, so we use Trello to move our design concepts from ideation to execution. Would be interesting to see what you guys could do to work around that!

@georgeallen Curious- what's been your biggest pain point using Trello in the design concept process?

@moiz_alam So right now- the most common request is from marketing and growth teams looking to start prioritizing tasks within sprints, and monitor their dependencies with their engineering team (for e.g. a customer commitment with a major release- or a product announcement). We're about a month away from rolling out our teams functionality to allow teams outside of engineering to run their own sprints, and also view priorities (+ team stats) on their dashboard.

@moiz_alam @ibamasood that’s interesting - I thought it’s mainly for engineers but didn’t realize it’s for marketers too.

@moiz_alam @adnandawood We thought so too- until we started receiving requests from growth teams to run their sprints. And we realized, most teams outside engineering don't log in to CI/CD or Git to understand and view progress on releases. PM software typically requires a ton of manual configuration to set tasks to PRs/commits. Marketing, growth and sales teams need to be continuously in the loop of releases for customer commitments and product launches. It's been an interesting use case outside of engineering.

@emily_santiago Hey Emily! We're introducing the teams concept in May. Since it's coming really soon - feel free to just have everyone in the same org for now (and use requirements to group by department).