The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Modify Project Lead / Default Assignee fields on next-gen projects

TL;DR

Admins can now modify the Project Lead and/or the Default Assignee fields of a next-gen project

 

What has shipped?

When a next-gen project is created for the first time, the Project Lead and Default Assignee fields default to certain values depending on certain factors and the type of project. In Classic, these fields are available in the Project Settings → Details page and the project admin is able to change the values in these fields at will. In next-gen, however, these fields were not available for modification and the defaults set during project creation were not modifiable by any actor related to the project (project admins, Project Lead, etc.).

We are very happy to announce that admins can now modify the Project Lead and Default Assignee fields for all Jira Software and Jira Service Desk next-gen projects.

 

How do I use it?

Customers can choose to edit the Project Lead and Default Assignee fields by following these steps:

  1. Open the Project Details page available under
    Project Settings → Details

    Screenshot 2020-07-22 at 10.50.52 AM.png

  2. Here, two new fields ‘Project Lead’ and ‘Default Assignee’ are now available

    Screenshot 2020-07-22 at 10.53.12 AM.png

  3. You can assign any user as the Project Lead as long as the user has site access in which the next-gen project belongs.  

  4. You can choose either Unassigned or Project Lead as the Default Assignee. If you choose to set the Project Lead as the Default Assignee of a project, please ensure that the user has viewing access to issues of the respective project. Please note, that the Unassigned option may not be available if it has been disabled by the administrator.

  5. Press Save

 

This release finally gives next-gen admins greater control over these two important fields of a project and puts an end to the need for time-consuming workarounds.

Have any questions or feedback, please comment on this post and we’ll get back to you as soon as possible!

6 comments

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

Taranjeet Singh
Community Champion
July 30, 2020

@Arjoon Som Thanks for sharing. Next-gen projects are on a roll....continuously improving.

Rodney Marable
July 30, 2020

When will this change be available for the Server product?

Like Kathy Yu likes this
Sarangam Birru
June 2, 2021

We are trying to modify Project Lead but it is not happening. Please suggest me how to resolve this issue.

Like Kathy Yu likes this
Marcel Becker
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 26, 2021

For us, the query for the "Project lead" dropdown is not working. It's not suggesting any users and with that, it's not possible for us to change the project lead.

Like Kathy Yu likes this
Kathy Yu
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 6, 2022

It's still not working on Jira Server Product.

Marek Lumtzer
September 15, 2022

Is it somehow possible block possibility to change project lead? where and how? cause ownership/or project lead can be changed to anybody in the company but without any notification. can be set it managable only by admins?

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

TAGS
AUG Leaders

Atlassian Community Events