nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I set a system-wide default user?

George Carvill

I am trying to setup a trial UserVoice HelpDesk interface to JIRA using Go2Group's add-on. The documentation states this prereq clearly:

"Make sure "Allow unassigned issues" is switched on in JIRA General Configuration"

That is obviously not acceptable as a global setting. All our JIRA issues have to be assigned to some person. Not doing this results in no sync and errors like the one below in the log:

2014-03-14 14:06:45,872 QuartzScheduler_Worker-0 INFO georgec com.go2group.services.UserVoiceServiceImpl:job [jira.issue.fields.AssigneeSystemField] Validation error: Issues must be assigned

I have default assignees for all the projects. But I was wondering if there was some way to setup a global assignee to see if it would satisfy the requirement. I am very uncomfortable lifting the assignment requirement globally.

The only other idea I can think of is to edit every step of every transition in every workflow to make the assignee required.

I have, of course, contacted the Go2Group support folks, who are researching.

Anyone here have any other ideas?

Accepted answers

George Carvill

Apparently I cannot.

All comments

Nic Brough -Adaptavist-

There's no way to have a global default user - that's the point of "unassigned" and "single assignee only". A global one would completely defeat the purpose of requiring an assignee - you might as well allow unassigned issues because it will mean exactly the same as "global default" - it's not been assigned to a real individual.

George Carvill

Actually, it would not be the same as I see it. I would assign myself as the default user. If something ended up assigned to me, that would get my attention and I would deal with

Nic Brough -Adaptavist-

Then how do you distinguish between issues assigned to you, and those that should be assigned to someone else? It's a lot more clear to have unassigned issues and keep an eye on those.

George Carvill

I don't distinguish! If they are assigned to me, that means I have to do something about them -- even if that something is to assign them to someone else.

If an issue is assigned to nobody then nobody will do it.

George Carvill

Apparently I cannot.

Ubisoft1

Hello,

A quick idea would be to add only in your post function of the create issue of all your issue type :

something like this :

import com.atlassian.jira.ComponentManager
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.security.Permissions
import org.apache.log4j.Logger
 
def log = Logger.getLogger("com.onresolve.jira.groovy.autoassign")
def componentManager = ComponentManager.getInstance()
def currentUser = componentManager.jiraAuthenticationContext?.user
def permissionManager = componentManager.getPermissionManager()
 
log.debug("Auto assign script for issue " + issue.key)
if (! issue.assigneeId) {
    if (permissionManager.hasPermission(Permissions.ASSIGNABLE_USER, issue, currentUser)) {
        log.debug("Assign to current user " + currentUser.name) //or assign it to you
        issue.assigneeId = currentUser.name
    }
}

So if a issue is auto/unassigned it force assign it to the reporter (or you could force it to you) this would make sure nothing is unassigned.

But our company actually work with unassigned, and we just have JQL tracking the unassigned issues.

Martin

Bharath Venkatesh

Get started with the latest version of UserVoice Plugin for JIRA.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

go2group