Application

Who would benefit? The Release date (internal) drives many of the OOTB reporting functionality in Aha! so it must be maintained and accurate for reporting to be accurate. For many teams, the end date of the release and the Release date (internal) ...

We attach a lot of ideas and/or features to epics, initiatives, and goals. That level of granularity is not needed in the presentation itself or the initial webpage view, in which we display only high level planning objects (initiatives, epics, go...

What is the challenge? Currently, status category is not a field that can be added to a customised card layout What is the impact? Status category can be indicative of the higher-level status grouping of where an item is at in our product ...

What is the challenge? I can design card views for the entire roadmap and want to put release date on the Now column but not the next or Later due to the level of commitment the farther out we get. What is the impact? Sharing release dates for now...

What is the challenge? Delivery risks are a great way to keep track of work that is at risk for a variety of reasons. Our challenge is we use various custom fields What is the impact? We don´t have a way to validate custom fields are filled or com...

What is the challenge? Currently in the prioritization view the Rank field sometime skips numbers (1, 2, 5, etc.) What is the impact? This makes it difficult to determine how many artifacts are in the list especially if this data is export...

What is the challenge? AI search cannot filter records by specific keywords. What is the impact? Slower discovery of relevant items and extra manual scanning to find records (e.g., requirements or ideas) that mention a term like “video.” ...

What is the challenge? For product team members who conduct a large volume of user interviews, it is challenging to keep track of the large number of participants and who was spoken to in which interview. A visual reminder of the participants th...

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 ...

What is the challenge? Be able to handle value from audit without deduced the "impacted" json field changes and without process the current string provided in "value" by sending both value separately to let developer handle them on their side if...