map story points to time estimation for scheduling release. For example, 1 point = 1 hr, 10 points = 10 hrs, etc.

We score our ideas and features with the same scorecard and would like to preserve this score when promoting an idea to a feature for easier backlog prioritization.

Understand how we are delivering on a capability. It looks like this was just removed???

Right now, the vote section on an idea record via the SF integration only shows a value if it is an opportunity record. This is nice, but it ignores the evaluation of impact to existing clients value they may have which is tracked in subscription ...

The key (IPLM-E-56) is worthless to external recipients and most business users. Instead, it reveals some inner workings (order it was created, how many, and some organizational info) that we don't want to share. So, I'd like to be able to hide th...

We noticed that when adding features from the initiatives panel, each feature gets assigned the start + duration of the initiative, resulting in a stack of features that have very long estimates. Not sure that should be the default behaviour, sinc...

It does not appear to be possible to move/copy Epics and Features from one Story Map to another. This is as essential as the ability to pick a post-it from one white board and stick it on another: at allows re-partitioning of the problem and exper...

Aha! Feature may contain Requirements from different Jira Projects. Right now, the fixVersion is synced with "fixVersion ID", which will not be synced successfully when the Feature (Epic in Jira) and Requirement (Story in Jira) belong to different...

Right now, you can link an already created idea at the Salesforce account level, but you can create a new idea. This has been requested from many of our solution architects supporting current customers. Would be a big help in encouraging additiona...