Re-enable conversion of Features to Requirements when JIRA integration is active

In some cases, people add stories in JIRA for a release linked to Aha that are not part of an Epic. This can result in the JIRA story appearing in Aha as a Feature (at the same level as JIRA Epics), due to how the integration is set up. Previously it’s been fairly easy to clean this up as you can convert each Feature to a Requirement in Aha under the correct Feature, and this change would be reflected in the linked JIRA story (the Aha reference would be updated). However since the update in June (http://support.aha.io/hc/en-us/articles/209360886-Release-Notes-through-2016-06-17) this is no longer possible, and requires a somewhat lengthy and tortuous manual resync between Aha and JIRA to get the issues linked correctly. It would be massively helpful and remove a lot of frustration for project admins if the Feature to Requirement conversion feature could be re-enabled when the issue is integrated with JIRA, while taking care to avoid the potential data integrity problems that were identified that triggered this change in the first place.