ADD A NEW IDEA

Jira

Showing 168

Map to a persona name value in integrations

Right now we leverage personas to describe who a release is targeting, where we'd love to be able to push the text value into our JIRA mapping
Barnett Klane over 4 years ago in Jira 3 Future consideration

When an integration update comes from JIRA, it would be useful to see the "integration" completed the update in history instead of the callback user.

The callback user usually is not the one making the update in JIRA. It is almost 100% someone else on the technology side and not the product team. JIRA indicates that the integration updated the JIRA issue. It would be nice if Aha did the same.
Wen-Wen Lin over 5 years ago in Jira 5 Future consideration

Ability to create JIRA integration thorough Aha API

We have teams with several projects and creating it through templates is not practically scalable, hence require an API to create JIRA integration manually
Guest almost 7 years ago in Jira 3 Future consideration

Manual Sending of Requirements to integrated development tool

Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
I R 12 months ago in Jira 2 Future consideration

JIRA integration needed at the portfolio and product family levels.

We use initiatives at all levels within Aha and need to be able to integrate those with JIRA for additional capacity reporting. If initiatives are available to be entered on those levels, it would be useful to have the integration setup available ...
Wen-Wen Lin almost 5 years ago in Jira 2 Future consideration

Support bulk remove of JIRA links from "Features List"

Currently, JIRA links must be removed one at a time. On occasions, we'll find ourselves having to do larger bulk operations, and the manual removal of each link by clicking on the feature is time-consuming.
Guest almost 8 years ago in Jira 1 Future consideration

Support for Jira Code Markup

Need to support the Jira code markup option. If the developer enters sample code as part of the description in Jira, the description gets updated in Aha! However the code markup is translated into very large tables in Aha! At some point, Aha! u...
Guest about 8 years ago in Jira 2 Future consideration

Product Line initiatives linked back to Jira Epic

We have the following workspace hierarchy; Product Line A Product B Product C Each Product is setup to integrate with a different Jira Project. If I create a feature in Product C and link it to an initiative in Product Line A, the following happen...
Bill Simakis about 4 years ago in Jira 1 Future consideration

Auto Resend all Fields per release

Right now, even after we manually click "Send to JIRA" for the first time for a release, subsequent changes to that release ( for eg. Addition of a feature under that release) do not automatically go through to JIRA. We'd want to have all changes ...
Guest over 5 years ago in Jira 2 Future consideration

Map one Aha release to several Jira projects

We have several Jira projects aiming towards the same release. When importing fixVersions from several Jira project to one product in Aha we get one release for each project/integration in Aha. This means that if we have 10 projects aiming for the...
Guest over 5 years ago in Jira 0 Future consideration