All ideas
Sort by:
Trending
Filter by:
Status
Showing 8637 of 8637
1
VOTE
Release date changes - require reason and display on retrospective
Who would benefit? Teams analyzing the changes in a release and needing to understand the factors that contributed to date changes. What impact would it make? Better visibility into challenges or themes to impacts on releases. How should it work? ...
0
Future consideration
2
VOTE
Add option to transfer work request name to resulting record
With this idea, it became possible to automatically add the description from the work request when accepting and promoting: https://big.ideas.aha.io/ideas/A-I-12674 It would be helpful to have the same option for the name of the resulting record. ...
0
Future consideration
7
VOTE
7
VOTE
Automation - Support for updating scorecard values
We use Scorecard ranking to prioritize which features should be worked on for each release. Problem is that we have thousands of tasks, features, bugs and nearly impossible for us to rank every feature. We upgraded to enterprise+ because we wanted...
2
Future consideration
8
VOTE
Measure and show time spent in status including non-discrete time
It would be quite a feature if every entity possessing status would have a small UI area showing time spent and in detail graphical representation of non-discrete time spent in each status. Maybe it could be gantty, but importantly, it should show...
2
Future consideration
13
VOTE
Competitor Enhancement & Battle Cards
Our company has a portfolio of 30+ products, organized into several product suites, with various packages sold across 5 different markets (and the sub-markets within them). We need a better way to handle competitors:
Create Competitors at company...
1
Future consideration
2
VOTE
Relates to functionality is terrible
When trying to relate two cards, the search functionality is embarrassingly bad. If I know the prefix of the card to be related, I should be able to put that in as a search term. Instead, it appears to only be searching on card titles.....so I can...
1
Already exists
9
VOTE
More control over UI User Story Map: Features organized in 2 columns under a single master feature & step
When working with many features, it is important that Features in User Story Map can be organized in two columns or more under a single master feature and single column per step. Currently each column must have a master feature * at the top of eac...
0
Future consideration
6
VOTE
9
VOTE
Allow requirements to be associated with the release record
The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...
0
Future consideration