Currently there is one option for selecting the items when creating an AHA!-JIRA integration, the JIRA project name. In our system several teams are using more than one JIRA project so in this way we have to set dedicated integrations for each JIR...
We build features across several releases or we break them into smaller marketable components of the larger feature. We really need a way to tag a feature to multiple release vehicles.
Brooke Huling
about 9 years ago
in Features
10
Shipped
It would be helpful if we had the ability to copy a requirement to the same feature. We use requirements as product backlog items. Sometimes they are too big. It would be useful to be able to copy a requirement as the first step in splitting it.
We often use various lists and reports. Unfortunately, their utility is limited due to the fact that filters are only inclusive. We'd like to see filters built with the ability to exclude certain things (i.e. tags, keywords, dates, etc)
It would be very useful to bulk edit requirement fields including:
Requirement assignment
Requirement logged effort
Requirement status
Requirement original estimate
Requirement logged time
As a product manager who manages multiple products and has a development team working with multiple productsI would like a straightforward way to prioritize features across productsSo that I can communicate to my developers what our highest priori...
Daniel Schwent
over 5 years ago
in Features
3
Shipped
Currently, users have the option to show or hide sections on the related tab but they do not have the ability to hide the key results section on features, epics, initiatives, etc. Users should be able to opt to hide and show the key results sectio...
The Feature Progress field is a very effective visual of Feature % done, but there is no option to map the Progress from the JIRA Epic record using the Epic % complete value which is derived from the number of completed stories for the Epic.
Our I...
Barry Kinner
about 5 years ago
in Features
11
Shipped