ADD A NEW IDEA

All ideas

Showing 6011

Function as a hub to push data from JIRA to DevOps

We use JIRA internally for tracking most of our development work, while a customer we work for uses DevOps. We also use Aha. We would like our customers to be able to see JIRA comments pushed through to DevOps. We tried to use Aha as a 'hub' to do...
Guest over 1 year ago in Azure DevOps Services and Server 2 Future consideration

Text wrap for thick bars with text inside

Text inside the bar is useful, as it takes up less space on the page in most cases, and makes it 100% clear which item you are referring too on the roadmap. However, when the name of the item is long, then the text runs off the bar and this looks ...
Andrew Brooks over 4 years ago in Roadmaps 0 Future consideration

Master epics should automatically inherit start and end dates from the release dates where the epics reside

With a master epic you can enter a start and end date, or have it be automatically calculated. The problem/idea is that this automatic calculation of start and end date should be based on the release dates for the releases in which the epics reside.
Guest over 3 years ago in Epic 2 Future consideration

Remove 'Will not implement' items from the Develop workflow board

If the workspace status of a feature/record is set to 'will not implement' then ideally it should be removed from the workflow board in Develop too.
Todd Meyer about 2 years ago in Workflow boards 0 Future consideration

Show story maps associated with a story or epic

Promoting Story Maps to a first class object would enable users to: list story maps list and select stories in a story map for bulk operations list and select epics in a story map for bulk operations Sometimes I want to tag all the stories associa...
Guest over 4 years ago in User story map 0 Future consideration

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...
Guest about 5 years ago in User story map 0 Future consideration

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...
Guest about 5 years ago in Jira 0 Future consideration

Bulk edit release phases

It would be great to be able to modify the attributes of a release phase using bulk edit. Example may be when a key milestone (common to all releases) needs to change across multiple releases. This would not be a common release date though (which ...
Justin Woods over 4 years ago in Releases 2 Future consideration

Add a column in a custom table that is automatically updated with the last date and time the row was changed/updated, and another column to track the last user that updated

This would help us keep track of how and when entries in custom tables are updated, and to make sure this is happening with enough frequency. We use custom tables for many business critical functions.
Guest over 4 years ago in Application 3 Future consideration

Maintain record links when promoting an idea to an existing feature

When promoting an idea to a new record, the dependency linkages get carried over from the Idea to the new record. However, when promoting to an existing record, this does not happen. We rely on this carry over so that PMs do not have to do extra m...
Ankar S over 3 years ago in  0 Future consideration