Expected behavior when adding a Record field to a layout is that when records are selected, a relationship link is created. Use Case: We need to drive people to link specific records and leveraged Record Fields; i.e. one or more release, one or mo...
Guest
almost 5 years ago
in Features
1
Future consideration
When creating a copy of a feature, the record links are also copied over. However, it would be really useful if at this time a new "Relates to..." record link could be created to link it to the copied feature.
I often use the "copy" functionality...
Guest
over 5 years ago
in Features
3
Unlikely to implement
As a product manager, I would like to be able to split a feature so that I can release part of it even though the whole thing is not ready.
We use requirements as product backlog items and sometimes we complete several of them and want to release...
Tom Beck
about 6 years ago
in Features
0
Future consideration
Allow a user to set his/her default view based on Saved Views
I have set up Saved Views for Features, Releases, etc. I would like to set one of those Saved Views (per page - Features, Releases) as MY default view. Without this feature, every time I navigate to a page, I have to go to Views, click which view ...
Guest
about 6 years ago
in Features
5
Already exists
Capacity bars on features and requirements that show when logged work has gone over original estimate
Capacity planning (when enabled at the product level) shows work remaining, work done and work over capacity at the release level in the form of coloured bars (green, blue and red respectively)
It would be very useful if this same graphical treatm...
Guest
over 6 years ago
in Features
0
Unlikely to implement
Add internal field name to CSV exports to make importing simpler
It would be super helpful if CSV exports of lists were given a second header row to include the internal field name in addition to the friendly name for each column which is exported right now.
This would be really useful for those wishing to expo...
Guest
over 6 years ago
in Features
0
Future consideration
to control the amount of information that flows from JIRA to Aha I tend to create the Feature first in Aha and then link it with the corresponding Epic in JIRA. Next i import the stories associated with the Epic by going on the integration -> I...
Markus Gujer
over 6 years ago
in Features
2
Future consideration
Currently each custom field, e.g. in Feature detail is listed in an extra line.
The fields are very short, so a lot of unused space is wasted right of the fields.
It would be very helpful to arrange the custom fields the same way like it is possib...
Alexander Vukovic
about 7 years ago
in Features
1
Unlikely to implement
Reviewers should be able to copy features into products they own
As a product owner, I should be able to to copy any feature of which I am a reviewer into any product that I am product owner or contributor on. I may want to reuse majority of the feature for my product, and make slight tweaks without needing to ...
Guest
over 7 years ago
in Features
0
Will not implement
Add optional date fields or ranges on Requirements
Allow Requirements under features to have Date fields. These could be locked to the feature's date range or allowed to fall outside depending on the organization and how they manage.
This would allow for more granular reporting on Features, or t...
Travis Allen
almost 8 years ago
in Features
4
Unlikely to implement