Skip to Main Content
ADD A NEW IDEA

Jira

Showing 170

Flag Feature/Story as had been deleted from integration

While I understand the desire to never delete a feature or story either in Aha or the integration partner (Jira in my case). I would like to see a feature that flags the deleted item in Aha as being removed. This would allow me to manually review ...
Kenny Burnham about 4 years ago in Jira 1 Future consideration

Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field

Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field - prevents having to go to JIRA and add points individual after time spent planning in AHA! - efficiency for PMs and Engineering
Guest over 6 years ago in Jira 1 Future consideration

Auto-sync of sprint field between JIRA and Aha

We implemented the sprint field mapping and have found that the sync isn't quite automatic. When we rename a sprint in JIRA - that shows up as a new sprint value along with the old one. This happens a lot and currently we run into a lot of confu...
Guest over 5 years ago in Jira 2 Future consideration

Support multiple scrum boards

Some Jira projects leverage multiple scrum boards within a single project; it would helpful if the Aha! integration could accommodate that.
David Strathy-Miller over 2 years ago in Jira 0 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 almost 2 years ago in Jira 0 Future consideration

Support Movement of Requirements to Different Features in Other Workspaces

We recently integrated JIRA stories mapped to Aha! requirements but are running into an issue with stories moving from JIRA epic to JIRA epic. Currently, Aha! supports stories moving from epic to epic, but only if those epics are mapped to feature...
Anh Truong over 3 years ago in Jira 1 Future consideration

Set feature initial status on "Send to jira"

It would be nice to have a status set on the first send to jira. I have for example configured in jira integration page: Status "New" in Jira -> Status "In design" in Aha. So when I click the "Send to jira" button in the feature is should...
Szymon Lukaszczyk about 7 years ago in Jira 4 Future consideration

New "integration reference" custom field type to house read-only text reference to a field on other side of Jira (or other) integration

There are fields in Jira (and I imagine other integrated applications) that don't map cleanly to an Aha custom field type. I am proposing a new custom field type that is an always-readonly text field that can be mapped to any Jira field type, and ...
Gene Lewin about 2 years ago in Jira 0 Future consideration

Allow child integrations to inherit the "run-as" user from an integration template

The following idea is for the JIRA integration, but could describe integrations to other development tools using a similar web hook mechanism. The integration template functionality allows settings from a master template to be adopted by child in...
Justin Woods over 4 years ago in Jira 0 Future consideration

Need easier way to link to existing Jira records!

Current workflow from what we have determined and as was suggested by Aha support: 1. A new idea/suggestion comes in from a customer, we promote a new requirement in an existing Feature. 2. It is promoted to a new requirement. 3. Within about 30 s...
Jon DeLong about 2 years ago in Jira 0 Future consideration