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?
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.
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"
This worked for me for a Next Gen Service Desk.
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
Hello, Atlassian Community! I thought it would be fun to do something different for my teams' last retrospective of 2019 so I'm planning to do a "year in review" with info-graphics. Wha...
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