All ideas

Showing 9010

Assignee does not get sent to Jira if using Default Assignee functionality

If you use the "default assignee" functionality, then that assignee will not get sent to Jira, even if that user exists in Jira. This could be considered a bug.

Avigail Ehrenhaus about 9 years ago in Jira 0 Already exists

1 VOTE

Define and link to Delivery Channels

It would be useful to have built in “Channels” as an entity having their own attributes) and allowing Features / Initiatives / Releases to be related to one / many channels. The way we organise AHA is to have our products that we want to deliver ...

Andy Darrant about 9 years ago in Application 1 Will not implement

1 VOTE

Attach an existing to do/task item to an existing feature

Editing an exisitng To Do does not allow to attach to existing feature

Guest about 9 years ago in To-dos 0 Unlikely to implement

1 VOTE

Delete trello card associations less aggressively

When a user is working on a feature in Aha that is linked to a Trello card, if she accidentally changes the release for this feature to the release of a different product (e.g. the Demo Fredwin cycling product), the trello linkage is immediately d...

Angus Davis about 9 years ago in Trello 0 Unlikely to implement

1 VOTE

Improve display of the Iniative > Feature hierarchy in pivots

If I add Initiatives and Features to the Cells section of a pivot table (not Rows or Columns), the display is a little funny. It lists all the features and prepends the Initiative with a dash in between. It would be better to see more of a hierarc...

Jonathon Leeke about 9 years ago in Reports 0 Already exists

1 VOTE

Add the name of the Release into the features shown on the Workflow board

This would be really useful for seeing at a glance who is working on what Release. As you can see from the attached screenshot, we have our designer working on three 'Design' features but from the Workflow view we're not able to see which Releases...

Guest about 9 years ago in Features 0 Unlikely to implement

1 VOTE

ability to edit requirement name

Current: I don't seem to be able to edit the requirement name field after saving it; at least, there is no intuitive way to do it. Target: allow the name field of requirements to be edited directly in the feature view.

Max Cascone about 9 years ago in Features 1 Already exists

1 VOTE

An automated function for E-mail-documentation

Let's say I ask a number of product related compliance questions to our legal department, and I would like to document them in Aha. It would be a really cool feature, if you could send the email directly to your aha-domain e-mail and it would auto...