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

Crucible create issue - default project

Jeff Storey1

In crucible, I know I can create an issue directly from a review comment. The create issue dialog shows the first project in the list of jira projects alphabetically. Is there a way to link a crucible repository to a specific project so when I select create issue it defaults to that project?

Accepted answers

rstephens

Hi Jeff,

There are two ways you can control this:

1. If the Crucible review is linked to a JIRA issue, this JIRA project will be preferred

2. You can create an entity link from the Crucible project to the JIRA project. Inline issue creation will default to use the primary link if one exists.

Kind Regards,
Richard Stephens

All comments

rstephens

Hi Jeff,

There are two ways you can control this:

1. If the Crucible review is linked to a JIRA issue, this JIRA project will be preferred

2. You can create an entity link from the Crucible project to the JIRA project. Inline issue creation will default to use the primary link if one exists.

Kind Regards,
Richard Stephens

Jeff Storey1

Thanks, #1 did the trick.

Kelly Schoenhofen

Are we positive #2 works? The default Jira project selected when creating an issue from inside a review in Crucible is always the alphabetically top project in Jira, in spite of an application link between the correct Jira project and the Crucible project.

#1 does work; the moment you link the review to an issue, issues created from inside the review do indeed pick the correct project.

I can open up a support ticket to get this fixed, if anyone can confirm #1 is indeed not working. It's a minor annoyance to us, since creating Jira issues from a code review is just starting to happen here.

Kelly Schoenhofen

#1 does work; the moment you link the review to an issue, issues created from inside the review do indeed pick the correct project.

I can open up a support ticket to get this fixed, if anyone can confirm #2 is indeed not working. It's a minor annoyance to us, since creating Jira issues from a code review is just starting to happen here.

Jeff Storey1

I haven't tried #2 since #1 works here for us.

Welcome!

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

Quick Links

Find more posts tagged with

jira

fisheye-crucible