ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 240

Support the ability to change a Jira project key

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox over 2 years ago in Jira 0 Future consideration

Inform user if Version export to Jira fails due to existing fix version in Jira

Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...
Guest 4 months ago in Jira 0 Future consideration

Use Custom Table data in Integration with Jira

Need to functionality to include Custom Table fields in the integration mapping. We created a new table for Aha Roadmaps for Program Increments. The table is linked to both Epics and Features, to simplify the reports (same value for both). The cha...
Edgar Holguin 4 months 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 4 years ago in Jira 2 Future consideration

Ability to create a report of integration errors across multiple workspaces

Currently the only way to look at the integration errors across multiple workspaces is to bring up the Integration Updates dialog and use the Send outgoing changes tab. But you can't filter on error text, or expand the window to see the everything...
Jor Bratko about 2 years ago in Jira 3 Future consideration

Improve integration job troubleshooting steps

To help me quickly troubleshoot background job logs: Tag each Update all linked records job type with the integration name. You are already doing this with Integration Import job types. In the case where a background job has failed, you write in t...
Alfred S about 1 year ago in Jira 0 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 about 8 years ago in Jira 8 Unlikely to implement

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 about 6 years ago in Jira 3 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 about 5 years ago in Jira 0 Future consideration

Have users in Jira and Aha matched for comments, updates etc

I realise this is not Aha's fault, but if we put the issue here with more info, users will be more likely to go to Jira to vote for the issue there. Currently whenever someone comments on an issue in Jira, in appears in Aha as a comment from the ...
Guest almost 9 years ago in Comments / Notifications / Jira 1 Unlikely to implement