Application

My idea is to integrate “AHA Idea link” within feature as soon as AHA idea push to Rally as a Feature We have separate URL for AHA idea therefore to check all critical information like Idea submitter, Business Owner, Comments, Business Justificati...

What is the challenge? During studies/interviews, certain themes can arise related to customer feedback. These can be related to things like sentiment, jobs-to-be-done, or categories of topics. However, today there isn't an ability to mark or repo...

What is the challenge? We have a product with several modules within it and we would like to group release notes by the product modules, then by Feature Type. What is the impact? We have to increase Feature Types to include module names making rep...

What is the challenge? There are a number of views throughout Aha! where record cards are used to display information and can be filtered for multiple workspaces. The challenge is knowing which workspace each record belongs to without having works...

Who would benefit? Any client, but especially those practicing SAFe What impact would it make? Make it very clear which features can be pulled into a PI and which won't, based on capacity, so negotiations can commence! How should it work? On the C...

We use the initial estimate field for early product planning. While the "No detailed estimate" field helps for our detailed planning stage, we want similar functionality that checks for missing initial estimates to support our earlier planning.

We have a use case where we want to automatically send a link to the idea associated with a feature to Jira. We thought the way to accomplish this would be to include a custom field on the feature that we then populate through an automation rule, ...

When we review features with stakeholders, we need to consider and refine both the description (user problem) and the acceptance criteria (definition of done) before it can be approved. We also need the acceptance criteria to sync to an equivalent...

The release retro report currently uses only a single (pseudo) milestone: when development started. Some teams want to measure changes in the release relative to several milestones within a release, such as a beta launch, or code freeze.

I'd like a dedicated board for managing a products goals and initiatives. My company uses agile principles even at the highest level of a product as our goals are taken through various stages such as research, development and validation and I woul...