Show JIRA # rather than Aha # on Roadmaps

JIRA came first at our company, and only a handful of users use Aha -- consequently, when I publish a roadmap, it is assumed that the issue numbers shown on the roadmap are JIRA issue numbers -- this creates a lot of confusion. I would like to be able to either show the JIRA issue numbers, or hide the issue numbers altogether. 

  • Cameron O'Rourke
  • Nov 22 2015
  • Unlikely to implement
Release time frame
  • Dec 30, 2015

    Admin Response

    As described, the Aha! issue number appears on roadmaps to be used as an easy reference. While we can understand that there may be some confusion across the two platforms, one workaround would be to change the product prefix in Aha! so that it does not match the one used in JIRA (or vice versa).

    While some customers do use JIRA, we do not have plans to show the JIRA issue number on Aha! roadmaps.

  • Attach files
  • Joost Pisters commented
    May 03, 2016 07:26

    As our development team works fully in JIRA it is very difficult to give them a roadmap that does not include the JIRA numbers at least showing. Why not allow it in the "customize feature card" as one of the fields I could add?

  • Puneet Singhal commented
    December 08, 2017 19:45

    I do not understand this reasoning.  Organizations should be able to define what their "primary key" is.  There is no harm in having an Aha #, but could it not be configured in such a way that the "display key" is configurable at a product/line level?  Why force different teams to talk in a different language (#s)?