Skip to Main Content
Status Future consideration
Categories Roadmaps
Created by Michael Vitalo
Created on Apr 6, 2024

Link by Reference ID should work even after converting the record to another type

What is the challenge?

When I convert an Aha feature (say, https://mycompany.aha.io/features/PRODUCT-870) to an Epic (say, https://mycompany.aha.io/epics/PRODUCT-E-20), the original link no longer works and returns a 404. This is horribly confusing if the link was shared in Slack or email. The user literally has no clue where the record went.

What is the impact?

Users have broken links that don't link to the converted object, rendering old meeting notes and Slack messages useless.

Describe your idea

All links should work forever (unless the object is deleted). I should be able to convert something up the data model and the original link for the Feature that is now an Initiative should still work - redirect me to what the object became.

  • Attach files
4 MERGED

Don't lose the link to requirement

Merged
If I create a feature from requirement - link to that requirement doesn't work anymore. Since URLs are different for features and requirements (they are not unified like it is in JIRA), could we at least have URL redirect to new feature URL? This ...
Mia Rucevic almost 9 years ago in Features 0 Future consideration