I've looked around, and found answers that told me that this is most likely because my default assignee does not have the assignable permission (gee, thanks.) The problem is, the default assignee for my project DOES have the assignable permission. It's set via a project role, which the default assignee (also the project lead) is a member of. We do NOT want to allow issues to be created unassigned. Where else can I look for what might be causing this issue?
Yup, it was the components. Wow, how unintuitive. I can see how you might want to be able to set a different assignee for a specific component, but it seems to me that if you don't have anything specific set in a component, it should inherit from the project's default assignee.
Here are some screenshots to help clarify; maybe I'm missing something. In the Issue Permissions screen, you can see that the Assign Issues and Assignable User permissions are set to use the Users project role.
Bigger version (http://www.flickr.com/photos/hookedbyesther/9917333125/)
In the Project Role screen, you can see that the default group for Users is jira-users:
Bigger version (http://www.flickr.com/photos/hookedbyesther/9917367026/)
And on the People screen, you can see that JIRA Monkey, our project lead, is part of the jira-users group.
(Bigger version http://www.flickr.com/photos/hookedbyesther/9917500853/)
What am I missing that would allow us to have JIRA Monkey be the automatic assignee of tickets created?
Yes, it is the People tab. I see that you attached it now.
Btw, where does it say that default assignee doesn't have assignable permissions? Can you check if you have any components and a component lead doesn't have the permission but is set as the default assignee?
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