In Next-Gen projects, I have NO way of
1. set default assignee
- tried adding a rule to set assign when moved to To Do status in Kanban board. It only works when it is "moved to" To Do status. Not when an issue is created and "placed in" To Do status.
2. assign a workflow to issues
- previously, when created a project, there was auto-generated workflow for the project. I couldn't find it so I created a workflow and associated to the workflow scheme. Now, I can't find place to associate this workflow scheme to my projects.
Next-Gen is great, but missing something should be very "default" for the users.
The approach you given is NOT working for me. Because, the issue state is the default state while creating the JIRA.
In case, when someone creates a JIRA the deafult state is "TO DO" and I use the same rule to assign the JIRA to me when the JIRA moves to "TO DO" state, but still the jira is getting created "Unassigned".
Is there any other approach or better way to configure the Automatic/Default assignee?
Took me ages, but finally figured how to add a default assignee for Next Gen Issues.
Just open any existing issue (existing, not new), click Automation rules on the right hand side.
Add a new rule with 'Issue creation' as the trigger, save, then set the assignee.
Now they will always be assigned the issue once it's created. Be aware it can take 2 seconds, so it will be created with unassigned, and then almost instantly change when the rule is run from the trigger.
I assume we no longer need an assigned lead for projects, as this does exactly the same, but with more control - albeit slightly harder to set up ... though only once, and really only a few more clicks than Classic.
I think it's sort of better overall, but needs more UX management to make it easier to set something which seems a pretty obvious control.
There's a way to do this for Next Gen projects. I don't remember the original source, but go to:
https://[account name].atlassian.net/secure/project/EditProject!default.jspa?pid=[PID NUMBER]
account name - first part of your URL
PID NUMBER - your project ID
Then you'll be presented with a page that lets you change the Project Lead. I had to go thru trial and error to figure out what my Project ID was. If there's a better way to list out the Project ID, I'd love to know.
Thank you Sarwar! This worked for me. I found a way to reliably determine what a NextGen project's pid is, although it is a little convoluted:
I mean, depends on your usage. I'm using it to manage a three person IT team, and while a bit annoying I can't track time, it's not something that I necessarily am dying to utilize. Our Development team is a entirely different thing, and it would break their processes if it didn't have time tracking.
To that fact, only my IT team is on the "next gen" platform. Just feels like we're being willing participants in beta testing something new. Overall I like it.
Yes none of the above tricks work. No sure why anyone would want to prevent automatic assignee, but if there is another work around please publish. The only real use I can see from the next gen projects are for simply to do type projects. I am using it for requests for improvements to the other Jira projects.
You can setup an automation to do it. It is an impressively over engineered workaround but it works.
There a number of clicks to get through but it is fairly straight forward to create a rule to do this.
@Cory ToddIndeed it now works! There is a newly added trigger "Issue created" that does the trick. A few months ago, it wasn't there (only "issue transitioned" trigger was there). Thank you!
Still, if you want to go for something more simple, you can install the free app Classic Settings for Next-Gen projects, that Sarwar Faruque suggested in the answer below
(https://marketplace.atlassian.com/apps/1222170/classic-settings-for-next-gen-projects?hosting=cloud&tab=overview). You then get a "default assignee" field under Settings/Apps/Classic Settings.
Big thanks for sharing this, @Jean Canazzi!
We naturally hear how Classic Settings brings back missing options (and we love it!), but offering next-gen project admins a time saving alternative for essential configuration needs is definitely a plus worth mentioning. Even more when I think about bigger and bigger organizations moving to next-gen, and facing large amounts of projects and admins.
Check out this app - Classic Settings for Next-Gen projects
It's free and does exactly what we need.
Hi @Sarwar Faruque,
Thank you so much for mentioning our app. Seeing it shared by active members of the community is just amazing. We are so happy that you find it helpful, and really appreciate you sharing it and helping others.
Hi @Nikki Kim,
We totally agree that next-gen projects are great!
This is exactly why we created Classic Settings. It lets you configure the project lead and default assignee for next-gen projects the same way we are all used to from classic projects. Your specific use case is totally covered, and everything works for Jira Service Desk too.
The app currently does not offer a solution for that, but other features are going to be covered soon, and we are open for feature requests and ideas...
I found another way to do this.
Go to Project Settings --> Request Types
Choose the Request Type
Click Edit workflow
Click the Create bubble
On the right side, click the + button under Rules
Click "Assign a request to someone", click Select
Type in their name and click Add
This worked for me for a Next Gen Service Desk.
There is another way to obtain the PID for the projects
You can use the REST API to list the projects
The response will have the pid
curl -X GET \
-H 'Accept: application/json' \
-H 'Authorization: Basic xxxxxxxxxxxxxxxxxxxx'
"description": "Your Description",
"name": "XXXX Sandbox",
"name": "TEST PROJECTS",
"description": "Jira test projects for testing purposes"