-
Sub-task
-
Resolution: Fixed
-
None
-
None
Update on 22nd July 2020
Hi Everyone,
We are very happy to announce that Project Lead and Default Assignee fields are now modifiable for all next-gen projects on Jira Software and Jira Service Desk. It may take a day or so to roll out to 100% of projects. More details here: https://community.atlassian.com/t5/Jira-articles/Modify-Project-Lead-Default-Assignee-fields-on-next-gen-projects/ba-p/1438466
We apologize for the delay and hope that this helps our users leverage next-gen projects more effectively moving forward.
Regards,
Arjoon Som
Sr. PM, Jira Cloud
Problem Definition
User is not able to change Project Lead on existing Agility Project type
Suggested Solution
Add the functionality for user to apply Project Leads to Agility Projects
Workaround
Take the current issues for Agility project and bulk move them to a different project type
- https://confluence.atlassian.com/jirasoftwarecloud/migrate-from-a-next-gen-project-to-a-classic-project-957974933.html
- Alternatively, Atlassian Support is able to manually update the Project Lead.
- Using cURL, you can be able to change the Project Lead of a next-gen Project. Please generate an API token here
curl --request PUT \ --url 'https://<your-instance>.atlassian.net/rest/api/3/project/{projectId}' \ --user 'email@address.com:API-TOKEN' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json' \ --data '{ "leadAccountId": "5d3b06xxxxxxxxx", "projectTypeKey": "software", "key": "ABC" }'
You will have to run this via a Terminal, enter the details of the new users by using the accountId, this can be gotten from https://<your-instance>.atlassian.net/people then search for the user to know the accountId which is in an alphanumeric String. Secondly insert the correct project id and project key on the Script prior to running it. This endpoint is gotten from our documentation for Update Project
Alternatively, if running curl is proving difficult especially towards Window users, you can download this Free software called Postman which is able to Perform HTTP request. Please do the following to easily change project lead of next-gen projects.
Step 1: Make sure you have Administrator Project role on the next-gen Project
Step 2: Get Postman, and do the below Settings as shown on the images.
| A | B | C |
|---|---|---|
 |
 |
 |
Step 3: On the Image A, Click on Authorization tab and select Basic Auth, enter your email address and API token following the guide from here
Step 4: On the Image B, Configure the headers as shown on the Image and change the HTTP request to PUT. Please indicate the URL as https://<your-instance>.atlassian.net/rest/api/3/project/ABC
where ABC is your project key.
Step 5: On the Image C, please make sure you add correctly this JSON post
{
"leadAccountId": "5d3b06xxxxxxxxx",
"projectTypeKey": "software",
"key": "ABC"
}
Where leadAccountId is the accountId of the user you want to change to. Final result should be a 200 OK HTTP Status, which means the Project lead has been changed.
- duplicates
-
JSWCLOUD-18375 Being able to change a project lead
- Closed
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- relates to
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
[JSWCLOUD-17323] As a project administrator, I want to be able to define and change a Project Lead in a next-gen project type
Hi Arjoon Som and other Atlassians,
Congratulations on the release!
As big fans of Jira and the vendors of Classic Settings we're very excited to see this out! Obviously we think next-gen projects are awesome, and we're really happy we can be a part of it. We hope our app was helpful with this issue for you guys too. If there is any way we can help, like something you guys think we should communicate to our users, please let us know...
Hi there to all of our classic users here,
Huge thanks for all the love and shares here, in the community and in our reviews!
You guys are all awesome and we really appreciate it. Special shutout to Stefan Slawidis, FUN MAN ANDY, John Gates and Mauricio Jimenez Miranda, who shared here among other places.
I also want to take this opportunity to let everybody know we tested using the new features side by side with Classic Settings, and everything works as expected on both ends. We invite you all to stay with us as we continue evolving the app to help in more ways. It will of course stay free and we’re going to keep supporting the project lead and default assignee fields. I’ll post more on our reasons and intentions in the community. Please send feature requests – we want to help.
Lastly,
We made a short classic video for the app and I thought everybody here might enjoy it. I recommend using headphones or speakers. Hope it makes you smile and compensates on the long comment.
Have a great day everybody,
Addown Support
Hi Everyone,
We are very happy to announce that Project Lead and Default Assignee fields are now modifiable for all next-gen projects on Jira Software and Jira Service Desk. It may take a day or so to roll out to 100% of projects. More details here: https://community.atlassian.com/t5/Jira-articles/Modify-Project-Lead-Default-Assignee-fields-on-next-gen-projects/ba-p/1438466
We apologize for the delay and hope that this helps our users leverage next-gen projects more effectively moving forward.
Regards,
Arjoon Som
Sr. PM, Jira Cloud
Small oversights like this and the general performance of Next Gen is just embarrassing. Why is this product even in production?
Unfortunately after 1 year of using Next Gen I'll be moving back to Classic for my team.
Hi Everyone,
Due to unforeseen circumstances, we've had a last-minute hitch with the rollout of this feature. Over the past couple of days, the team was working on resolving this hitch, but this hitch appears to be a problem that will take some time to repair. We felt that taking a step back and ensuring that this feature works for 100% of our customers on JSD and JSW was better than putting something out now, which would not work for certain key use cases for customers.
In light of this decision, the new date for the launch of the Project Lead and Default Assignee for next-gen is 22nd July 2020. We are committed to this date, and several teams across Jira are working together to resolve this ASAP. We understand that this news is not favorable, and we apologize for this unintended delay.
We will post another update on the progress of this rollout on 16th July 2020.
Thank you,
Arjoon Som
Sr. PM, Jira Cloud
How did this "miss" get into a released version of Jira Cloud? This is wild.
This ticket was written 29 January 2018. Today is 6 July 2020. This is planned for release tomorrow. That's over two years!
Hi Everyone,
Just a quick update. The release date for this feature continues to remain 7th July 2020. Please expect a formal announcement then.
Regards,
Arjoon Som
Sr. PM, Jira Cloud
Hi Everyone,
We are happy to share that the team is working on the finishing touches and that we are scheduled to roll out this feature on the 7th of July'20. More information will be shared on this forum and on the Atlassian community next week.
Regards,
Arjoon Som
Sr. PM, Jira Cloud
Hello, Timo:
Unfortunately, it seems that they are still working on something that will help us all... In the meantime let me share with you that I've successfully manage to change the Team Lead assigned to a NextGen project using an addon called "Classic Settings for Next-Gen projects" by "Addown Studio". It works flawlessly and without complications.
Any ETA on when we can expect the next "soon"-post? Not even the feature itself, just the post about it.
Hi Everyone,
Atlassian developers are continuing their work to enable this feature for next-gen projects and should be done with the development soon. I will update this thread as soon as more information is made available.
Until then, if you require changes to the Project Lead field, kindly open a request with support, and they will be happy to assist you in making the change.
We appreciate your patience and assure you that the enablement of this feature is a priority for us.
Regards,
Arjoon Som
Sr. PM, Jira Cloud
Hi, We are also running into this issue as well...is there any update? I didn't like that I had to delete the project and have my director created one project.
Hello - we are running into this issue as well.... it's early June. Is there an update?
Hi Everyone,
We would like to inform you that our developers are currently working on enabling Project Lead and Default Assignee for next-gen projects on JSW/JSD. While we cannot provide you with exact timelines at this point, we expect this work to be completed soon.
We understand how this issue limits the usability of next-gen projects, and we are working to make this feature available to customers ASAP. Kindly expect another update in this regard from us next week.
Thank you,
Arjoon Som
Sr. Product Manager
We are running into this issue now. What is the ETA? it says in progress? any update?
Is the default solution to request support?
Yes, please add this feature. I appear the technical lead on my new projects because I created the project.
OMG Thank you so much FUN MAN ANDY!, Classic Settings worked flawlessly!
As John Gates says, if this was such an easy fix, why does Atlassian keeps just ignoring this request? I mean, this one was raised almost two years ago!
If it's this easy to fix, kind of makes you wonder why Atlasssian has stone walled on it for so long...
Great to hear it's working just as great for you too John!
@hclarke: I've installed the free Classic Settings app from Addown Studios.
Works perfect! 
This is such a pain that we cannot update the project lead espcially when someone leaves and also makes doing an audit hard - Please sort this out seems like a pretty major flaw
Come on Atlasssian. Stop treating Next-gen projects as second class. If you want us to use Jira to manage modern development - READ Agile Development,) you need to provide basic Agile capabilities that at least equal Classic projects. It starts with this most basic of requests.
Sad that this feature isn't possible yet. But I tried the Classic Settings from Addown Studio and it worked, I was able to change the project lead without any hassle. I know this sounds like an ad, but really a feature this simple shouldn't be an external app. But I'm gratefull, that there is an fix for that, but I'm looking forward to an official solution from Atlassian.
Hey there,
Just wanted to let everybody know our team at Addown Studio created a new app called Classic Settings aimed at easing the transition to next-gen projects, and of course the first release does exactly what we are all looking for here - allow changing the project lead and default assignee the same way we always did in classic projects.
We really hope this app helps everybody with a quick solution that requires zero learning, and maybe even reduces some of the load from Atlassian's support team regarding this (especially in these times).
If you have any issues, thoughts or just want to ask for the next feature, please don't hesitate to contact us using our Service Desk or by email
and of course we would really appreciate reviews.
We hope you enjoy!
What is the Purpose of "NextGen"? NextGen doesn't have the Standard Jira Project features.
Hey guys!
Happy to see you're exciting about the news 
I'm just passing by to say, in this meantime, if you still need to change a Project Lead with some urgency, don't hesitate to open a request with us in Support.
We can help you with that.
Kind regards,
Gabriele Franck
Atlassian Support Team
Thank you for starting work on the same as this is a very basic requirement for projects .
YES! It's In Progress. AMAZING! Really really looking forward to this shipping. 
Hi Everyone,
Thanks for your patience. We have prioritised this work and we will be starting work on it very soon.
Regards,
-Mythili
360 votes, 219 watchers, 2 years... this is not an issue in a "forever backlog", this is an issue in a black hole!
Hope you can do it soon! Thanks @mgopalakrishnan @asinha
What do we need to do to get this prioritized? There's no add-on in the marketplace to fix this, so Atlassian has to do the work!
This has been over 2 years in the making. C'mon guys, these are basic functionality requests!
We are really hopefull to have this available as soon as possible. The sooner the better!
Hi All,
Thanks for your patience. While I don't have an exact ETA, I want to take this opportunity to let you know that we will be starting work on this very soon.
Thanks,
-Mythili
how incomplete next-gen projects are! lacking basic SCRUM functionalities (which is why I believe it was intended to do) just get back to classic
Please fix this, our "project lead" has not worked for our company in months.
Wrote an article about this on community. 🤓 Hopefully it will get Support so busy they'll realise it's more efficient to just ship this. 😝
I've given up on the workarounds.
Once a new NGP is created in our instance, I immediately raise a support ticket and within 1 - 2 hours the Atlassian support team have changed it for me on their end.
Efficient,fast and they're professionally friendly.
This for me is now currently the quickest and most sure fire way to change the LEAD on a NGP.
Yeah,
I am struggling from past two days in setting the Lead information running the curl script.
This missing feature is a bummer for same reason as stated above by @Abhinaya Sinha
In two days, this request for a 10 minutes development feature, is ONE year old... I am not impressed.
The feature is on settings page when seleting the Classic project type.
Also, please make sure that this is done for both Server and Cloud ! Thank you kindly.
@Abhinaya Sinha - what is the latest on this one.
This is really frustrating the Jira Cloud Admins.... many of us have strict company policies about restricting rights for creating projects. That means we have to create Next Gen projects and end up being the Project Lead which is completely not the desired end result.
I am waiting this update, too. I am disappointment with Jira Cloud.
Almost two years and this simple feature is not still implemented, really incredible. In my company have a bunch of next-gen projects where deleted users are listed as lead and I can change it. How is it possible that it was not yet fixed? 🙁
Yes - please fix. It is very misleading having the creator of the project becoming the Lead.
PLEASE URGENTLY FIX THIS ISSUE. I am removing the person who created the project off the team. Need him of the board.
PLEASE fix this issue. Allow the project lead to be changed in project settings. This impacts notifications and the ability to empower team leads with projects. This should be a very basic feature.
Thanks.
I agree that this is a 1 day change and seems crazy that Atlassian cant respond quicker to these required changes. Its not like we can work with Next gen without it.
Seriously? This issue has been open for nearly 2 years. This should take at most a day to fix. Either make it possible to change the lead or remove the giant PROJECT LEAD column from the UI so as not to confuse people. This is ridiculous.
Edit: Confirmed that the workaround using `curl` in the description does work, so this is really just a matter of adding one extra box to the project settings page. This was quite a few hoops to jump through for something so basic.
Not to be able to change the leader of the project feels like missing a very basic feature.
This is so prominent in the list of projects and doesn't allow for leads to change - our management team would find it far easier to track which project is run by which PM or lead if it was possible to change this. The field clearly exists and provides information back to users in the list of projects so it needs to be editable.
As the Jira administrator, I've just created a next-gen project for my company.
I don't expect to be the project lead for the entire lifecycle of the project.
I don't want to be contacted about the project when I'm no longer involved in it, but having my name as the lead is an invitation to the uninitiated.
I want to be able to delegate the lead responsability in the project settings pages.
I don't want to have to resort to any of the listed workarounds.
@abhinaya
This issue is created on 29/Jan/2018. It is almost 2 years now, but still open! Interesting!
I'd like to be able to assign the leads for each board to the proper employee, so that people know who to contact if they have questions.
My Story:
The original employee who created most of the boards has left the company. Since I joined, I have created some additional next-gen boards (for several teams). All of our company projects list either her or me as project leads now... and this is inaccurate.
FYI- I've even tried completely removing her from the system, and its still showing her as the lead (but has an "oops" when you hover or click on her... because, of course that user can't be found now.).
I setup a project but am not the lead and will not be involved long-term with the project. For larger organizations, it is very important that the project lead be accurate so that others know who to communicate with for project configuration and related administration questions, as well as project specific content.
Same, I looked everywhere and am the administrator of our cloud at the moment. I'm trying to transition all the project leads to the appropriate folks. We have only one project that it will not allow me to update because "Agility Project Type" was selected.
We also need this. Please implement it. People make projects for others. People quit or move to different projects.
Hi Everyone,
We are very happy to announce that Project Lead and Default Assignee fields are now modifiable for all next-gen projects on Jira Software and Jira Service Desk!
More details here: https://community.atlassian.com/t5/Jira-articles/Modify-Project-Lead-Default-Assignee-fields-on-next-gen-projects/ba-p/1438466
We apologize for the delay and hope that this helps our users leverage next-gen projects more effectively moving forward.
Regards,
Gabriele Franck
Atlassian Cloud Support Team