You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
All the issues are opened on the user that created the project, is there a way to change that?
I tried using the Rules Manager by creating a rule that sets the issue reporter as the assignee / or the current user rule, but it doesn't work.
Hi Tal,
Currently, it's not possible to choose a default assignee on next-gen projects. We have a feature request suggesting the implementation of this ability:
- https://jira.atlassian.com/browse/JSWCLOUD-17498
Please, click on vote and watch to receive updates about the feature.
For now, the default value is "Automatic" that will assign the issue to who created the project, so the user must select the "Unassigned" or pick a user as assignee.
Regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I actually managed to change it via API in postman:
curl --location --request PUT '{{env}}/rest/api/3/project/{{projectKey}}' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--data-raw '{
"assigneeType": "UNASSIGNED",
"projectTypeKey": "software",
"key": "{{projectKey}}"
}'
Worked perfectly
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Tal Levi,
You are right that rules are not a solution for this issue, but you can still solve it...
Besides voting and following JSWCLOUD-17498 (about default assignee) as @Angélica Luz correctly suggested, maybe you should also take a look at JSWCLOUD-17323 (about project lead). There is a lot more activity there, and the API solutions you'll find in the description can solve your issue too. You can really see how hard Atlassian's support team is working there, under a lot of pressure.
As for a complete solution inside Jira,
My team has an app just for that, called Classic Settings. It offers a straightforward solution for your issue. The app is free and here to serve the community, so please feel free to try it out and share your experience. We've been getting great reviews and our service-desk is always open.
No matter what solution you chose to use, I hope I helped!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Addown Support : Thank you so much, your addon is great! A shame that you have to solve Atliassian's issues - but thanks for doing it ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.