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; } } }

Use different issue type schemes for both Greenhopper and Jira?

Doug Varn2

Hi all,

Is this possible? I'm trying to have one project use 2 issue type schemes. For Greenhopper, I'd like to use one scheme (and have default as "Story") and then for Jira issues I'd like another (with default as "Bug").

To me, this will be the only way to keep QA people and devs/managers happy and not complaining why they're likely choice isn't the default.

Accepted answers

Christian Czaia [Decadis AG]

Hey,

you can only associate one scheme with a project. Greenhopper just uses the configuration you apply in your JIRA project administration...

Cheers Christian

All comments

Nic Brough -Adaptavist-

Greenhopper is a view on a project, not a separate structure. Everything in GH is inherited from the project (although there's a veneer of config on top of it, and it provides some extra stuff that the project can use)

Christian Czaia [Decadis AG]

Hey,

you can only associate one scheme with a project. Greenhopper just uses the configuration you apply in your JIRA project administration...

Cheers Christian

Doug Varn2

ok, was afraid of that. it seems useful to separate default options for new card in greenhopper (likely a story) and new issue in jira (likely a bug). maybe this will be a future enhancement.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-cloud

moderators