Share multiple versions of your Roadmap

You can now save multiple views of your Roadmap to capture configurations that you can return to at any time.

Customize each view's sharing settings to keep it private, share it with the product team or your entire organization.

When experimenting with views you’ve already shared with colleagues, any edits you make will only be pushed out for others to see when you save the view to publish your changes. 

Rest assured, no matter what view a feature is displayed on, its status and release will always remain up-to-date.

You can also now drag 'n drop features and releases to re-arrange them right from the Roadmap!

  • Note: Drag 'n drop currently limited to Roadmaps arranged By features.

If you'll be presenting the Roadmap off your screen before an audience, hide technical or internal-facing features – or upcoming bug fixes you'd prefer not to advertise. 🐛

More Roadmap updates on the way! 🤩

Saved view enhancements

You'll notice we've reflected the latest updates to saved views on the Features board as well. That includes drag 'n drop to re-order your views!

Portal events in activity log

When users update Portal cards, these changes will be reflected in the activity log of the associated feature/component: 

  • Added feature to Portal
  • Removed feature from Portal
  • Moved feature to new tab
  • Updated feature name, description, image

JIRA integration: Push features under the same component to multiple projects

For projects with productboard features mapped to JIRA stories...

Previously, two sibling features with the same parent component were always pushed to the same JIRA project. Now they can be pushed to two different projects. (Though they will miss each other very much.)

JIRA integration: Changes to Reporter & Assignee mapping

If you're using the JIRA integration, here's a small change you should know about. We're updating how reporter and assignee fields get populated when a productboard feature is pushed to JIRA.

Now it works like this:

  • The feature owner will become the issue reporter
  • The issue assignee field will be left blank

Previously it worked like this:

  • The user who pushed the feature became the issue reporter
  • The feature owner became the issue assignee

We made the change after learning that most of you consider the feature owner to be the product manager, whereas the JIRA assignee is the person actually developing the feature.

While you can't yet assign a feature to a developer right from productboard, at least it will be easier to see which issues still need to be assigned to someone in JIRA.

See also

Did this answer your question?