Using Agile Hive with existing Jira issue types — is it required to switch?

[sina afroozi]

Hi everyone,
I’m planning to start using the Agile Hive plugin in our Jira environment. We currently have a large number of active projects, each with its own set of existing issue types that are already in use.

I noticed that Agile Hive allows defining hierarchies at the project level, but it doesn’t seem to provide tools for managing or mapping hierarchies for issue types. Before moving forward, I want to clarify one point:

Do I need to switch to Agile Hive’s predefined issue types in order to use the plugin properly, or is it possible to continue using our existing Jira issue types without changing them?

If there are recommended best practices for integrating Agile Hive with custom or existing issue types, I’d really appreciate any guidance.

Thanks in advance!

[Joshua Brock _ Seibert Group_ GmbH]

@sina afroozi -

Greetings from all of us at Agile Hive, and thank you for giving us a try!

@Kseniia Trushnikova is correct, and they have passed along the correct link to reach out to our support team to get you the ongoing assistance you need to make your work a success!

Welcome aboard and we look forward to working with you!


Joshua
Content Writer & US Representative
Agile Hive (a product of Seibert Group, GmbH)

[Kseniia Trushnikova]

Hey @sina afroozi,

I’d suggest creating a ticket directly with the plugin’s development team. They will be able to help you faster and provide more complete and accurate guidance: https://agilehive.atlassian.net/wiki/spaces/GI/pages/526155777/Agile+Hive+Service+Desks