ADD A NEW IDEA

All ideas

Showing 6181

Allow 2-way syncing of attachments in Github integration

Currently attachments only sync 1-way from Aha! to Github. It would be ideal if attachments added via Github would be updated in Aha! as well.
Austin Merritt 11 months ago in  0 Future consideration

Display named range value on Overview tab "Initial estimate" field

Who would benefit? Teams using capacity planning for teams, planning with named ranges (e.g. t-shirt sizes) What impact would it make? Currently, the "Initial estimate" field includes the resulting time-based estimate, but not the range I've selec...
Reilly O'Connor 3 months ago in Capacity planning 0 Future consideration

Add ability to report on named range value

Who would benefit? Teams using capacity planning for teams, planning with named ranges (e.g. t-shirt sizes) What impact would it make? Today, I am only able to report on the specific estimate associated with a record, not the named range value tha...
Reilly O'Connor 3 months ago in Capacity planning 0 Future consideration

Embed notes in record description (same appearance as whiteboards)

Who would benefit? Product teams build up documentation relevant to specific epics and features. You can currently add this document to the Research tab or add it as a link in a record description, but this does not give a user a preview of what t...
Max Robbins 3 months ago in Notes 0 Future consideration

Determine default Home Page for All Users

When a user logs into Aha!, the first page they see is the page "How Aha! works". Our users are reporting that this is confusing, as they want to navigate to a page within the product itself (i.e. Feature Board or Releases Overview"). Users arrivi...
Matt Howard about 6 years ago in Account settings 8 Future consideration

Provide alternative way to match users when email address is not exposed in Jira

Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
Madeleine Black over 1 year ago in Jira 1 Future consideration

Re-use custom fields in any item type

It's cumbersome to need a unique custom field for the same data across different item types. It would be more efficient to be able to use a single custom field in multiple item types.
Max Cascone about 6 years ago in Account settings 7 Future consideration

Target, Commit and Stretch Lines in Feature Board

Similar to Capacity line in the feature board , we would like a target, commit, and stretch line with user defined % of capacity. Ex, 80% = commit, 100% = Target, 120% = Stretch with 3 lines. This way I could have a quick visual of my capacity in ...
Guest about 8 years ago in Features 1 Future consideration

Ability to report on work request status by workspace or team

When creating a report of work requests, I want to see the status (approved or rejected) for each individual workspace. Today, all workspaces appears on one line and show a status of 'pending' until all of the work requests are approved or rejected.
Shannon Sauvé almost 3 years ago in Reports 2 Future consideration

JIRA Service Desk Request integration with ideas

We have a central point of contact for users to get in touch with us. It is via JIRA Service Desk. To keep it central, but efficient, it will be good if a submission into JIRA Service desk can take a particular issue type and automatically submit ...
Guest over 7 years ago in Ideas 15 Future consideration