RELATED IDEAS
Allow auto-import of JIRA issue without the need for a "parent record" (or just a pre-defined default like with manual import)
I was a bit confused when I could import items from JIRA manually, and webhooks were working both way, but when I made a new issue in JIRA, it was not getting auto-imported. I read through lots of really long explanations about the need for "parent records", but the bottom line is that you guys are doing this via the manual import because we can define "release" on import.
I propose that you guys allow in the JIRA configuration to auto-designate a "parent record" when new issues are made in JIRA so that it's seamless and doesn't require another step.
In the meantime, I've just noted that I need to add a ticket to a version in JIRA before it shows up in Aha!, but I could see issues getting lost and causing issues. I can also see your users having issues with understanding this concept to use JIRA, so I think it'd aid in onboarding.
Similar issue here. Our developers don't perse use Epics or Releases. we only use sprints for combining them together.
And bugs don't get introduced to a jira project right away, in our environment we use Jira Service Desk to collect bugs and from there they are eventually forwarded to Jira.
Danny, I get it. But think about it from a JIRA perspective. You have people making issues willy nilly, and they don't always (or often?) link to anything, really. Someone finds a bug? They make a ticket. The whole problem with JIRA is that this gets unwieldy and it's hard to make sense of the barrage of tickets. And this is a problem that Aha! solves really well. So to force discipline in a place that is kind of inherently crazy so that you can get to the place where you actually impose the discipline and make sense of it all (from a product manager's perspective) seems like a bit of an ask when it'd be just as easy to have the product manager say, "ok, all that craziness in JIRA? Sure. I'm going to use Aha! to give me x-ray vision into it and not let the chaos prevent me from doing my job. Know what I mean?
Hi Casey, the product team will review this but just to clarify - the behavior isn't exclusive to the release -> feature parent child relationship. The auto import works for the relationships between: