JIRA does not let me specify "Unassigned" as a user name in the "Assign to User" field since this is not a real user name.
JIRA does not seem to clear the Assignee field if I specify to clear it when the transition happens (maybe Clear Field Value only applies to text/numeric fields).
I have a kludge which would work which is to create an artificial "mister.nobody" user and then use the "Assign to User" to do it, but I hate kludges.
Frankly, the assignee is to be left as the person who actually resolved the issue. Mostly otherwise, while looking up history data, you may land up in a state that you need to click and open each issue to find who resolved it. And also leaving the assignee with the actual user helps to dig out your completed statistics based on assignee which is useful in many ways.
I know I didn't answer your question, but was trying to explain the rationale behind the default workflow.
Clearing of the field as a post-condition of course works for Assignee too. Have you enabled 'Allow Unassigned Issues' in your System settings?
"Allow unassigned Events" is set to ON; this is what I see in the Admin settings and it is possible to manually assign an event to "Unassigned". Maybe it's a bug with version 3.13.3 (I know it's old but we're still in places on Internet Explorer 6. Yes, I know).
I think based on Renjith V argument, we will leave things as they are.
Thanks for your help.
go to workflow Edit work flow click on done transition and post functions add new post function
chose update issue field
issue field set it to assignee
field value Unassiged
click add and publish workflow.
Clear Field Value should work for Assignee as well. Are you sure the 'Allow UnAssigned' option is enabled? Also, what is the behavior when you add this? Does it changes assignee to a different user or the assignee remains the same?
I am sure allow unassigned option is enabled:
The assignee stays the same.
I have tested it doing auto-assign to a different role member or a specific user and that works
If you just want to find all unassigned issues through a JQL, excluding already closed issues:
assignee in (EMPTY) AND statusCategory != Done
The main point is often that you also need to store your value in the database:
import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.MutableIssue def issueManager = ComponentAccessor.getIssueManager(); MutableIssue mutableIssue = issueManager.getIssueObject(issue.id) mutableIssue.setAssignee(null); mutableIssue.store();
Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...
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