All ideas

Showing 9124 of 9124

Ability to click to zoom on images in description field

you should be able to click on attachments/images to view an expanded view of the image from the description box. Right now they appear in the description and many times are used to describe bugs or new features, however the preview is too small f...

Guest over 9 years ago in 2 Unlikely to implement

1 VOTE

Bulk Update Features

When bulk updating Features, I would like to use some literals and keys to update the existing values of all Features, as well as to reference to another field of that Feature, like: for each Feature add a prefix "XYZ_" to the value in field AAA f...

Christian Hartmann about 3 years ago in Features 0 Future consideration

3 VOTE

Integration with Collabnet

http://www.collab.net/products/teamforge Our development team uses Collabnet and as much as I would like to convince them to use Jira I do not think that is a realistic possibility, so this is a request for Aha to integrate with Collabnet.

Guest over 9 years ago in Wanted 0 Will not implement

1 VOTE

Dependency between tasks based on leadtimes

I'm look for an option to make a lead-time/dependency between two tasks. Within our cycles (life plants in this case), we have different tasks that are dependent of each other. If we sow in one week, we will plant 3 weeks after for example. We can...

Guest about 3 years ago in Dependencies / Features 0 Future consideration

1 VOTE

Add the ability to approve log time entries in Aha! Develop for payroll purpose

In Aha! Develop, having the possibility to log time entries approval would be great. Doing so, it could have a whole dimension of cost tracking as well and budgeting. Combined with time planning capacity per employee would top it all.

Anh-Tuân Légaré about 3 years ago in Sprints 1 Future consideration

2 VOTE

Add API support for retrieving integration details (target JIRA project + server url for example)

Allow automation of integration setup from other tools. In my use case, the intent is to be able to validate/cross-check what is actually configured on the JIRA side (admin only) with what is expected/desired on the Aha side (various project team ...

Guest about 6 years ago in Integrations 0 Future consideration

2 VOTE

Configuring workflow board should be reflected for all users

Currently, if I was to configure the feature workflow board (and/or feature cards on workflow board), the changes I made would only be reflected back to me. Every user of the workflow board has to then configure the board (and/or feature cards) th...

Guest about 6 years ago in Features 2 Already exists

1 VOTE

Adding people to paid seats in aha! develop is not as clear as it should be

I click into billing and see the open seats I paid for on Aha! Develop I click 'manage' assuming that would allow me to add seats to that arena of Aha! I get routed to Aha! Roadmaps with no clear way to get to the Users page of my Aha! Develop acc...

Guest about 3 years ago in Account settings / Development 0 Future consideration

1 VOTE

If I don't have access to a release, I should not be able to assign an Epic to it

Our company has many different workspaces and releases. And it is very easy to accidentally assign an Epic to a release that I don't have access to, just by clicking within the Release area, and without my knowing it, the Release has suddenly chan...

Guest about 3 years ago in Releases 0 Future consideration

3 VOTE

Add Jira "status" field

When working between Aha and Jira, it can be hard to tell what is being updated in each. It would be helpful to have a Jira "status" field that allowed us to definitively see the status.

Guest over 9 years ago in Features 0 Unlikely to implement

Share your product feedback

Please enter your email address

FILTER BY CATEGORY