We typically reference feature requests by the Aha feature ID, e.g. WEB-32 or WEB-44. When we push those feature requests down to Github for development, we generally create a branch for each issue, but since we lose this information it's difficult to recognize which branch relates to which Aha feature. I just manually prepended the feature id to the github issue names for our latest sprint...oh...the github integration updates Aha with the issue name. Hmmm...now my Aha features have the id listed twice. Well, not optimal, but I can live with that.
Alternatively, perhaps the integration could create a tag on the Github issue with the feature id.
|Release time frame|
Thank you for the note. As you mentioned, there is the workaround to include the feature ID in the name so that this information gets communicated. At this time, based on the existing workaround and current priorities, we are unlikely to make updates in this area. We hope you can understand.