Nikhil Kundra
Oh man - I
really
want to love this product (and I love the idea of it), but without being able to seamlessly read, edit, and update Jira Task Names, Descriptions, Comments, other fields, I am feeling more and more anxious using this and creating two systems of records I now have to maintain.
We use Jira so much (and of course have issues with its speed and UX) that it would be really helpful if I could filter Jira Tasks are assigned to me, are open (with a label that shows the swimlane/status it's in on Jira), are in the current sprint, and in which board (as I have multiple sprints running at the same time I am part of).
I really think the import Jira task, ticket status sync, and assign to calendar to block off fous-time are HUGE and WONDERFUL wins of your product, but if I can't sadly sync to Jira like I mention above... I get anxious about managing _another_ system (and Jira is already our source-of-truth); I don't want to manage two.
I really love what you guys have built, but I think it's missing a broader implication for Jira users.
Your UX and design sitting
on top
of Jira (like many things sit on top of Salesforce) to power your lightweight UX with Jira's robust set of complex (and often unnecessary features) would allow your solution to be a HUGE win for any company on Jira.
Please contact me if I can chat with you more. I'd love to use this and see a ton of potential.