RELATED IDEAS
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.
-
ADMIN RESPONSEDec 30, 2015
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.
2
MERGED
Align Issue ID between AHA and JIRA
In my organisation JIRA was introduced before Aha. When synchronizing between JIRA and Aha there will come a Unique Issue ID for Aha and the original Issue ID from JIRA will also be used for that Issue. Now you have two references for the same iss...
0
Unlikely to implement
1
MERGED
Hide Aha feature number on Roadmap
I would like to be able to hide the Aha feature number shown on the published version of the Roadmap. Rationale: On the public facing feature roadmap, Aha is showing the Aha feature number, which isn't known or useful to anyone since we are integr...
1
Unlikely to implement
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)?
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?