nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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!

Accepted answers

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

All comments

Kseniia Trushnikova

Hey @sina afroozi,

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)

sina afroozi

Hi @Kseniia Trushnikova

I followed your advice and contacted the Agile Hive support team through email. They responded very quickly and were really helpful. Here’s the answer I received from them:

What hierarchy level can be created between the numerous projects in play?: The hierachy level is based off of two core senarios. A FULL SAFe level with Portfolio layer, Large Solutions layer, an ART layer and a Team layer. The other scenario is based off of essential safe which some companies only want an ART and TEAM layer to work off of. In short, the herarchy configuration screen is very customizable to the needs of businesses.
Can we use existing JIRA issueType?: You can use your exiting JIRA issueTypes, but keep in mind that the standard issueTypes like JIRA "story" is universal and should continue to be used. You can also crate additional custom issueType like Risk and Objectives to fully utilize Agile Hive Reporting page if you desire.
Can we use existing workflow?: This is not exactly a question you asked, but I saw it in your email. The answer is yes, you can use your own customize workflow that you already have in place.
Are we restricted to ONLY use the pre-defined issueTypes from Agile Hive?: No, as long as issueTypes are within a project that is configured in the hierarchy level, they should be visible and show up on the PI Planning board under the correct PI Iteration tagging as well as the adjoining Sprint Iteration tagging.

Thanks again for pointing me in the right direction — their guidance solved my issue much faster than I expected.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-data-center

data-center

safe

plugin

agile-hive