Skip to Main Content
ADD A NEW IDEA

Jira

Showing 250

Project level automation with Jira

Requesting a change to Aha! Jira integration to allow for project level automation. Project level webhooks send payloads differently than system level payloads. If support for project level webhook payloads were added, we could enable multitudes o...
Guest over 1 year ago in Jira 0 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 about 5 years ago in Jira 2 Future consideration

Add more filters to integrations import

Who would benefit? aha admins What impact would it make? keeping Aha in sync with JIRA on the release. This would also help other internal stakeholders informed. How should it work? The integrations import desperately needs additional filtering cr...
Shri Iyer 9 months ago in Jira 0 Already exists

Allow To-Do's to be mapped to JIRA Issue Types

We would like to be able to make better use of Aha To-Do's so that they carry over to our JIRA Agile installation. Currently we have Initiatives mapped to Epics, Features Mapped to Stories and Requirements Mapped to a custom JIRA type of Requireme...
Guest about 9 years ago in Jira 5 Unlikely to implement

Including Dependencies in Jira integration at requirements/story level

We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
Trey S over 2 years ago in Jira 0 Future consideration

Defect: Jira Integration record mapping doesn't use custom terminology

Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
Guest 5 months ago in Jira 0 Future consideration

Ability to see more than the last 200 logs in Aha-Jira Integrations

Sometimes we need to investigate synchronisation errors between Aha! and Jira. We can find these errors long after an initial error might have happened. We might need to go back to the original error which may have happened months ago. The limitat...
Guest over 4 years ago in Jira 2 Future consideration

Support mapping JIRA Tempo Account field

When using the JIRA Tempo plugin to track work time, it is useful to link issues to Accounts - for this the plugin exposes a custom field named Account. This field, formerly called Billing Key, is used among others in reporting, to decide which cu...
Guest almost 9 years ago in Jira 8 Unlikely to implement

Populate Jira Components via Integration

Currently, as far as I am aware, the only way to use Components from Jira is to add a custom field in Aha! and map them. This works OK, however if a new component is added in Jira you have to manually add it to Aha! as an option to select. Please ...
Guest over 1 year ago in Jira 0 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