Skip to Main Content


Showing 168

Label the description box on the feature details panel.

When we create a new feature we populate the box labelled description which is mapped to description in JIRA - the user story. . But in the detailed view in AHA! that description text appears in a blank box. Are we able to label this description?
Guest over 7 years ago in Features 1 Unlikely to implement

Filter ideas by multiple references

I have a list of 50 idea references, which all would need the same action to be taken. Currently I can add "Search idea" filter to the list view. With that I can filter the idea's by reference or name. But only with one reference or name. It wou...
Antti Toivonen almost 8 years ago in Features 0 Unlikely to implement

Add ability to configure what sections are visible in the Requirements form

We might not want to initially use the Requirements sections due to our integration with TFS. It would be good to be able to hide sections on the Requirements form, and also be able to make the visible again should we decide to use that functional...
cheryl fetchko over 8 years ago in Features 0 Unlikely to implement

Show delivery of requirements across releases

Today there is no good way to show the delivery of requirements for one feature spanning multiple releases. For instance, if you have 3 of 4 feature requirements being delivered in Release X, but the feature itself won't be delivered until Release...
Micaela Heck over 8 years ago in Features 1 Unlikely to implement

Add a format painter in description fields

In all the description fields (in addition to bold/italic/underline/bullet points and so on), I'd like to have the "format painter" that exists in Office suite so that I can copy the formatting of a text to another text.
Emilie Takeda about 9 years ago in Features 0 Unlikely to implement

Initiatives, Features, and Requirements should inherit and display all upstream attachments

Please allow nested Initiatives, Features, and Requirements to inherit and display any attachments that were added 'upstream'. Oftentimes it will make more sense to attach documents like wireframes and GUI designs, data dictionaries, etc. to a 'pa...
Guest about 9 years ago in Features 1 Unlikely to implement

Logging working time on a feature

A user with reviewer status (non paying) should be able to log working time on a featureLogging working time on a feature. A person with reviewer status
Øyvind Standal about 9 years ago in Features 2 Unlikely to implement

Add actions to Transitions

It'd be great to kick off actions based on a particular transition. For example, if a feature goes from "Ready to Develop" to "In-Development", I'd love for it to be automatically sent to GitHub just by pressing that transition button. Obviously, ...
Guest over 9 years ago in Features 0 Unlikely to implement

Feature linked to multiple epics

Create ability for a feature to support multiple epics across workspaces. This will allow a single team that's working on a single feature that supports multiple epics across multiple teams. Currently we have multiple teams enabling a feature and ...
Steven Schafer 11 months ago in Features 5 Unlikely to implement

Use pagination to remove 50-user limit in Workflow view

When grouping by assignee, the view is limited to 50 users. Not 50 users at a time, but 50 users total. The truncation seems to be arbitrary as well, rather than picking, say, the first 50 users. I was informed that this is for performance reasons...
Guest almost 4 years ago in Features 2 Unlikely to implement