-
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
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.
Would really like this feature as a producer overseeing and planning projects for other project leads!
I am having this issue where I am unable to update next-gen project leads. Please add this feature.
This is also a problem for me also. Allowing someone to input a field upon project startup without ability to alter later is a shocking oversight. Tech support sent me here for this issue. We are comparing Jira vs. Zendesk and small stuff like this makes it hard for me to advocate for this product when small things like this are unable to be handled on the user/admin level. Can I add it? if yes I should be able to change or remove it. I feel like that is product development 101.
Jira Admin
added a comment - Same issue here. Please hide the project lead or make it changeable setting. This is misleading.
Jira Admin
added a comment - Same issue here. Please hide the project lead or make it changeable setting. This is misleading. I would recommend to write to tech support to Atlassian and see if they can assist with this.
Robert Skönblad Andersson
added a comment - This is an important function for me too. Now I'm the project lead of a project, but I'm leaving for a new job and I can't remove myself as project lead. That makes me concerned about what will happen when the other project admins delete my account? Maybe some features of the admin will be locked? Pretty stupid stuff.
Robert Skönblad Andersson
added a comment - This is an important function for me too. Now I'm the project lead of a project, but I'm leaving for a new job and I can't remove myself as project lead. That makes me concerned about what will happen when the other project admins delete my account? Maybe some features of the admin will be locked? Pretty stupid stuff. 
Gabby Sundstrom
added a comment - voting to change this also as without it, it is much harder to manage and assign work.
Gabby Sundstrom
added a comment - voting to change this also as without it, it is much harder to manage and assign work. 
Sara Bornes
added a comment - voting to change this. Created first next-gen project and definitely want to change project lead
Sara Bornes
added a comment - voting to change this. Created first next-gen project and definitely want to change project lead
Tom Leser
added a comment - @Tomas, I was not aware that support could even make this change. Yes then I will go ahead and do this because I need it for my dashboard visibility at our senior leadership team level.
Tom Leser
added a comment - @Tomas, I was not aware that support could even make this change. Yes then I will go ahead and do this because I need it for my dashboard visibility at our senior leadership team level. Hi everyone - one good way to make ourselves be heard is to submit support tickets every time we need a project lead updated. This will make the issue be felt internally and push it forward.
I'm not excited to have to babysit requests, but it might be the best path forward to get to the eventual goal.
Just wondering why is it taking so long to implement this small change? Is it really a BIG effort?
Can someone from Atlassian help us understand?
Tom Leser
added a comment - The "Projects" gadget's worth is severely crippled without this feature as an executive management's dashboard would certainly require this gadget, and who the project lead is should be critical information. Seems like a very simple update to implement. Please add this.
Tom Leser
added a comment - The "Projects" gadget's worth is severely crippled without this feature as an executive management's dashboard would certainly require this gadget, and who the project lead is should be critical information. Seems like a very simple update to implement. Please add this. This is confusing at best. If there is not a functionality to change the project lead, don't pre-fill the administrator as the project lead either. I am listed as project lead on all the next-gen projects I configured. Please consider adding this soon.
Pierre Thys
added a comment - We need this ASAP!!! I honestly can't believe that this is not in place. Next gen projects have great UX, but this is a serious miss.
I asked Atlassian support and got this reply:
"Reviewing the ticket, as of now there is no ETA on the bug fix. We are unsure on when the fix will be released. Due to more urgent and critical tickets on our developers plate currently, these tickets are currently being prioritized over less critical ones. For now, it will be better to perform the workaround advised in the bug ticket if it is being blocker at your end currently."
Don't hold your breath for a solution anytime soon.
This is kind of a serious issue. If the project creator is removed from the People list in the Project Settings, the remaining active users are blocked from creating new epics using the quick create + in the Roadmap. This needs a solution.
Any way we can get an update on this issue? We do not want to make a new project when a lead leaves.
Yes, please add this feature. I appear the technical lead on my new projects because I created the project.