-
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.
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