Open - 22 years ago

Last update - 7 years ago

Last update message - This suggestion is a priority for the JIRA development team.........

I think your definition of priority and my definition of priority are not the same.

Why is this seriously still 'Unassigned'? You lost this ticket because it is unassigned across all of Jira instead of just the project that it belongs to and no one is specifically watching 'Unassigned' issues in the project right? How about make this feature request a reality and this wont happen anymore. Hmm.

I agree with the others. Making an issue unassigned results in the ticket being lost as noone feels responsible for it. I also wonder why the assignee attribute is treated differently as other attributes. If you set the option to allow unassigned issues at least you should be able to have it required via field configuration scheme. Makes no sense to me, to treat it any different.

The fact that this is 'unassigned' offends me o_O 

Please make this feature a reality.  Without it, I'm being asked to create dummy accounts so that people can assign to them.  That is a terrible workaround, as it uses a license and doesn't clearly show what is happening.  Is that intended?  Are you trying to make using up licenses with fake users the workaround?  What is your workaround for this otherwise?  We sure do pay a lot for Jira these days, and as much as I care about 'New Priority Icons', I think you can do better with your time.

Come on Atlassian, SEVENTEEN YEARS for a common sense feature request.

Stop p****ing about with the UI for a while and develop some real features that real customers are asking for.

We need to be able to make the Assignee field Required as part of Field Configurations.

Our use case is to require Assignee at all times on Epics in specific projects so that there is a Point Of Contact for all the work in the Epic.

Using Workflow Validators for this leaves two loopholes:

1. The Assignee field on the Epic can be set to Unassigned, and that will not be fixed until the Epic goes through a Status Transition.
2. A Story can be "Moved" and changed to an Epic, and Assignee will not be required to be filled in during that process. Again, the problem won't be caught and fixed until the Epic goes through a Status Transition.

We lost 25 minutes in a meeting because you don't have this feature. Please develop this.

This issue was noted as being a priority for the development team since 2015 and it is 2018 and we still don't have a solution for this. It would be great since Atlassian recognized the utility of this feature in 2015 if it could be added to the project plan.

Thanks for all your hard work on Jira we all appreciate it.

Through the years, our team has received and continues to receive requests to enable the unassigned issues. The problem is that the unassigned issues does not work for all the projects and therefore, we cannot enable it. It is important that this functionality is configurable per project.