• 1
    • 13
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      It would be good to have more options for the default assignee.

      The usual options of Reporter, Single User, Custom Field in addtion to Project lead would provide greater flexibility. I currently have a project that would benefit from the option to set the default assignee as the Reporter.

      The ability for the user to list projects without a default assignee. 

      Workaround

      Create an Automation rule that will update the Assignee every time a new issue is created on the project. Smart Values can also be used for defined fields.

            [JRACLOUD-14897] More options for default assignee

            +1

            Priit Lahi added a comment - +1

            Hello,
            It would be great to get an update from Atlassian on this topic.

             

            Thank you

            Nicolas Le Corno added a comment - Hello, It would be great to get an update from Atlassian on this topic.   Thank you

            It would also be nice since you have the ability to set Component Leads in the given project if the transition allowed you to select 'Assign to Component Lead'. I understand thats a special concept and you can get around it to an extent for high level assignment of tickets but to give us more options by default would be great.

            Jessica Bartsch added a comment - It would also be nice since you have the ability to set Component Leads in the given project if the transition allowed you to select 'Assign to Component Lead'. I understand thats a special concept and you can get around it to an extent for high level assignment of tickets but to give us more options by default would be great.

            I've just looked at our database and 84% of our issues are assigned to the reporter. This means not doing this by default is a waste of time 84% of the time for us. I imagine this will be common in a lot of places (but equally understand plenty of places will be very different). Given that JIRA pitches itself as "the" Agile management tool, and an important part of Agile is trusting team members and being flexible to change (which we interpret as meaning they should be allowed to define their own work and hence raise their own issues), it's extremely odd that JIRA is insisting on this hierarchical idea of all issues going through the project lead by default. The "assign to me" button obviously saves a lot of time, but I'm afraid the post function is rubbish as it bulldozes over any assignment and is not transparent to the user. Neither have the same implication as having a default, which essentially says "if you raise it, you own it unless you make the effort to give it someone else", and hence I would like to also strongly request this issue.

            If anyone else wants to find out how many of their issues are assigned to the reporter, this is the script I used in JQL (unfortunately you need ScriptRunner to do this):

            issueFunction in expression("", "reporter == assignee")

            Paul Thomas added a comment - I've just looked at our database and 84% of our issues are assigned to the reporter. This means not doing this by default is a waste of time 84% of the time for us. I imagine this will be common in a lot of places (but equally understand plenty of places will be very different). Given that JIRA pitches itself as "the" Agile management tool, and an important part of Agile is trusting team members and being flexible to change (which we interpret as meaning they should be allowed to define their own work and hence raise their own issues), it's extremely odd that JIRA is insisting on this hierarchical idea of all issues going through the project lead by default. The "assign to me" button obviously saves a lot of time, but I'm afraid the post function is rubbish as it bulldozes over any assignment and is not transparent to the user. Neither have the same implication as having a default, which essentially says "if you raise it, you own it unless you make the effort to give it someone else", and hence I would like to also strongly request this issue. If anyone else wants to find out how many of their issues are assigned to the reporter, this is the script I used in JQL (unfortunately you need ScriptRunner to do this): issueFunction in expression("", "reporter == assignee")

            This shouldn't be hard to implement really and it would help a lot.

            Jonathan Drapeau added a comment - This shouldn't be hard to implement really and it would help a lot.

            +1. There's also a very popular Answers question about this: https://answers.atlassian.com/questions/59555/how-can-i-change-default-assignee-user

            Ændrew Rininsland added a comment - +1. There's also a very popular Answers question about this: https://answers.atlassian.com/questions/59555/how-can-i-change-default-assignee-user

            Mark Love added a comment -

            + 1 for this, but given it was first reported 6 years ago I'm not holding my breath!

            We would like to specify someone other than the Project Lead (Product Owner) to be the Default assignee.

            We use the "Project Lead" field in the filters for our agile boards, so I can't simply use this instead.

            I'd like issues that move to "Ready for Estimating", "Ready for Dev" or "Ready for Testing" to be assigned to pseudo users that we have setup for each team (Team Earth). But since these teams share a workflow I can't hardcode it. And I don't want to have to start enforcing the use of components to achieve this.

            Mark Love added a comment - + 1 for this, but given it was first reported 6 years ago I'm not holding my breath! We would like to specify someone other than the Project Lead (Product Owner) to be the Default assignee. We use the "Project Lead" field in the filters for our agile boards, so I can't simply use this instead. I'd like issues that move to "Ready for Estimating", "Ready for Dev" or "Ready for Testing" to be assigned to pseudo users that we have setup for each team (Team Earth). But since these teams share a workflow I can't hardcode it. And I don't want to have to start enforcing the use of components to achieve this.

            Sonya S. added a comment -

            hi,

            if I created a custom field which is a single select list (as drop down box).
            will it be possible that I setup default assignee associate with eash selection ?

            Sonya S. added a comment - hi, if I created a custom field which is a single select list (as drop down box). will it be possible that I setup default assignee associate with eash selection ?

              Unassigned Unassigned
              ab40276220d4 Greg Heap
              Votes:
              37 Vote for this issue
              Watchers:
              32 Start watching this issue

                Created:
                Updated: