Make URL fields clickable within views and notebooks

I've added a few links into our Feature object to track specs/mocks etc. Great that they're click-able from the page-layout - but I'd like to see this clickable from list views and notebooks. As an example, I've been adding some views into a notebook I'm sharing with cross-functional stakeholders, however, they need to copy/paste the URLs to access the content. Would make a lot of peoples lives' much easier if these were directly clickable.

  • Steven Kaplan
  • Apr 27 2016
  • Likely to implement
Release time frame
  • Attach files
  • Admin
    Zach Schneider commented
    May 17, 2016 22:56

    Hi Steven -- just following up to get some more context before implementing this idea. Which view are you adding to the notebook -- the feature detail view or a different one? And are you referring to PDF or web notebooks (or both)?

  • Zach Rose commented
    May 24, 2016 23:17

    I'm not Steven, but have the same request :)


    For me, the most pressing issue is the feature detail view (<domain><Feature ID>), and it would be very useful in both PDFs (first priority, personally) and web notebooks (second priority).

    I think ideally, all of the links that show up in the Report>List view would also be clickable in the notebook view.

  • Admin
    Zach Schneider commented
    May 25, 2016 02:53

    Hey fellow Zach -- thanks for the additional information :)

    For the feature detail view, are you referring to "internal" links such as "@Aha User" or "#Aha Feature", or "external" links such as ""?

    We already make external links clickable in PDFs and web notebooks, at least in the feature detail view; so if you aren't seeing those links as clickable, then that's a bug I'll need to follow up on. If you're referring to internal links, we intentionally avoid linking those in PDF and web notebooks because internal links will only work for Aha! users, and we presume that you're exporting to a notebook so you can present/share data with stakeholders outside of Aha!

  • Admin
    Zach Schneider commented
    May 25, 2016 03:42

    (We also avoid linking things such as the release name from a feature detail view in notebooks, for the same reason -- if that is what you were referring to.)

  • Zach Rose commented
    May 25, 2016 12:05

    Thanks for the reply, Zach! 

    I see what you mean. My use case is that some in the organization strongly prefer to look at something like a PDF list of features when perusing the backlog. I can easily generate this list using Reports, and then I can export it to a notebook. When in Reports in Aha, if I click a feature, the details pop up to the right (the link is specifically to https://<domain><Feature Ref ID>). But after publishing, that link becomes inactive.

    It would be beneficial for me to keep those direct-to-feature links active in notebook PDFs to help my organization transition to Aha. Long-term goal is to just have everyone going to a list view or other place in Aha to see the backlog, but that's a big jump in the near term. Having a PDF that links directly into feature details in Aha would be a strong transitional step.

  • Admin
    Zach Schneider commented
    May 25, 2016 21:53

    Thanks for the added explanation. We're revising the status of this idea down to "Likely to Implement" for the time being. We do plan to support the use case you describe in the future, but it is somewhat more complicated than my original interpretation of this idea, as it requires us to also add a setting for whether a notebook is for internal use (should keep internal Aha! links intact) or external use (should omit internal links).

  • Harmeet Gill-Sethy commented
    May 17, 2018 19:03

    I second the ask/use case that Zach Rose describe. Now that it's 2 years later, has this been implemented? If it has, would love to know how we can do this. Thanks!