RELATED IDEAS
Keeping link to Jira when disable an integration
When we disable an integration to Jira, we mean it to be we have a new Jira project to integrate to. It makes it easier on the integration on the feature to not have a huge list of Jira projects to integrate to and only to the projects that are active. We like having the link to the Jira epic no matter the status of the feature or what project it's enabled to so we can still get back to the work the feature entailed. Long story short, we are not excited that when you disable an integration, it removes all the links to the Jira epics. Not sure why this happens - you would think it would mean you no longer can integrate to that specific Jira project but can still get to the history of the work completed. The ask is that those links stay on the feature no matter if it's linked to the Jira project or not.
© 2024 Aha! Labs Inc.•All rights reserved
We've run into this so many times. If an integration needs to be updated to use a different/new project in Jira, we have to have two integrations running - one for the old project and one for the new. It makes it really messy to know which one is actually the "active" integration. If the links could remain, or you could just update the project in an integration, that would be wonderful!
Not only do we lose the ability to quickly go over to the Jira epic in order to see all of the issues that made up the epic, we also lose the percent complete on the feature that is integrated from Jira. It may be okay to lose the link and you must search on the title in Jira to find the epic, but if you try to run a report, you will have a lot of zeros on shipped features when it's actually 100%.