Hello Zoho Projects Team,
We would like to raise a concern and submit a feature request regarding the Jira → Zoho Projects migration process, specifically around how Jira connections are handled.
When setting up a Jira connection for migration:
Zoho Projects allows importing one or more Jira projects.
However, once a migration is completed, the Jira API keys are deleted and the connection is removed from zoho project - while still exists in Jira.
As a result, each new migration requires recreating the Jira connection, generating new API keys, and reconfiguring the integration again in Jira.
Practical Challenge:
In real-world migrations, especially for large or sensitive environments:
Migration is rarely done in a single batch.
We often migrate project by project, validating each one before proceeding.
Requiring a new Jira connection for every import introduces unnecessary friction:
Repeatedly deleting and recreating connections in Jira
Reissuing API keys and secrets
Increased risk of configuration errors
Slower and more error-prone migration process
Importantly, the Jira connection itself is already live and valid. The limitation is that Zoho Projects does not allow reusing an existing connection for additional imports.
We request the ability to:
Reuse an existing Jira connection (with the same API keys and credentials)
Perform multiple import operations from Jira to Zoho Projects using that same connection
Allow administrators to explicitly decide when to:
Reuse an existing connection, or
Revoke and recreate it if needed
Enables safer, staged, and controlled migrations
Reduces manual overhead and configuration errors
Improves migration experience for teams moving from Jira to Zoho Projects
Encourages adoption of Zoho Projects as a Jira replacement
We believe this enhancement would significantly improve the migration workflow and align better with real-world enterprise migration practices.
Thank you for considering this request.
Kind regards,
Ram