Crucible Jira Issues are going unassiged?

Hi,

I am creating Jira issues through crucible but it is going unassiged please help me regarding this..

4 answers

1 accepted

0 votes
Accepted answer

Did you add users to the project for which you are creating the issue in JIRA. After adding the users you can assign the issue explicitely....

0 votes

Set up issues to be assigned to Project lead by default or to Component lead by default. Or do you want to assign to specific people on issue creation?

Sir we want to assign to a particular user?

as in crucible we are getting option to choose the user, still we are choosing the user name in crucible but still it going unassigned.

please help sir.

Does that user has assignable permission in the project you are creating the issue?

Didnt understand your statement "as in crucible we are getting option to choose the user". AFAIK Crucible does not have a feature to select who will be the assignee for the issues created. The user you specify is used to create the issue.

Why don't you assign a workflow condition for the sub-task type that you have mapped in Crucible to assign the issue to a particular user.

And if you can tell me what is the reason for such a usecase to assign all the issues to a single person?

Once after creating your review, go to Edit Details>>Reviewers(when you click on this it will show the added users) you would be able to add only users who has been added to the particular project for which you are creating the review>>Done.

Thanks for the update, we are able to get the users name in the dropdownlist when we create review

We are assigining to a particular users, who has access to the project in JIRA (both JIRA and Fisheye use LDAP credentails only)

The issue is created, but in JIRA its unassigned - though in JIRA we have made settings "Allow unassigned issues as NO", the same we did while integrating the JIRA with fisheye aas well

Somebody please help on this, this is very critical for us??????

If you like the answers....mark it as accept...

But as stated earlier our problem is still same.

we are creating issues from crucible and still issues are going unassigned in our JIRA.

"The issue is created, but in JIRA its unassigned - though in JIRA we have made settings "Allow unassigned issues as NO", the same we did while integrating the JIRA with fisheye aas well"

Please help us regarding the same.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in Statuspage

How do your teams prepare for really high (planned) traffic days like Cyber Monday?

Hi there! Shannon from Statuspage here.  👋  With Cyber Monday quickly approaching, we're looking to hear from Atlassian customers – specifically from teams who touch incident response li...

44 views 0 4
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you