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?
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
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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
An efficient enterprise content management system, or ECM, is a must-have for companies that create work online (cough cough, all companies). If content calendars, marketing plans, and bu...
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!
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