ADD A NEW IDEA

Application

Showing 7532

Enable "record relationship" field types to be sent to Jira

Currently, record relationship field types can't be sent to Jira. We'd like to be able to see these fields in Jira so we can report on them.
Avigail Ehrenhaus over 5 years ago in Features 4 Future consideration

Manage collaborators

For presentations, it would be helpful to 'manage collaborators' at the permission/role level, rather than having to select specific users.
Jeff Shaffer over 2 years ago in Presentations 2 Future consideration

Add field to capture date of "last change" on internal and external release date

Changes in release dates need to be communicated to several stakeholders. If there was a "last changed date" field for both the external and internal release dates, a report could be generated to show all release dates that have changed in say the...
Ryan Bradley over 2 years ago in Releases 1 Future consideration

Enable Conversion of Product Workspace to Product Line

In the creation / setup phase of workspaces and product lines, we cannot change the workspace designation to a product line. Instead we have to move the data objects from the existing workspace to other workspaces, then delete the workspace that c...
Roger Octobre about 4 years ago in Account settings 1 Future consideration

Ignore Zero estimate values when calculating the Best Estimate

Today, if the detailed estimate is 0 then the Initial estimate is ignored in the best estimate calculation. I would expect us to ignore null/zero detailed estimate values if the initial estimate is >=1 when calculating the best estimate.
Gary Cohen over 1 year ago in Capacity planning 0 Future consideration

Simplify UX for To-Do's and Comments

Our engineers use Trello which is incredibly easy for them to use, though nowhere near as powerful as Aha. However, like Piovtal, Trello makes it incredibly easy to add comments. You just tap or click into the comment entry input box, just like us...
Angus Davis about 9 years ago in Comments / Notifications 2 Already exists

Remove Requirements from custom Feature Card layout

We would like to remove "requirement" from our custom feature layout as this adds "too many layers" to the work. We want to utilize "to do" only within our workspace.
Carolee Snarr almost 4 years ago in Features 2 Future consideration

Attach an epic to multiple releases

Using SAFE terminology, I have epics (master features) that relate to multiple program increments (releases). I'd like to be able to assign a master feature to more than one release at a time.
Guest over 5 years ago in Releases 0 Unlikely to implement

Allow dashboard read only users to easily open the report behind the panel

When we create dashboards we set them as read only to avoid any unintended changes being made to them however the dashboards are designed to be used by users to trigger action, so they need to be able to easily get to the filter behind the panel. ...
Eamonn Corrigan about 3 years ago in Reports 1 Future consideration

Aha and JIRA integration comment

What is the challenge? When linking with Epics in JIRA, if the title of the Epic in JIRA has a "-" in it, the comparison field for the name doesn't show any character before the "-" What is the impact? slight annoyance of having to put the correct...
Guest 5 months ago in API 0 Future consideration