Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

All the issues are opened on the user that created the project, is there a way to change that?

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.

3 answers

2 accepted

1 vote
Answer accepted

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

Voted, thanks :) 

Like Angélica Luz likes this
0 votes
Answer accepted

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

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!

@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 ;)

Like Addown Support likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Team-managed projects

4 steps to get actual statuses on the Jira board.

Jira   is a powerful tool   that helps teams to plan, manage, and report on their work.   We love using Jira, especially for its ability to track issue progress. But how to monitor the...

1,241 views 10 14
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you