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; } } }

assign an issue to a group or a non-paying dummy user?

Gil_2dvf2c

hi guys,

I know this was available in the server instance of Jira. But we are really missing this one on the cloud instance.
Sometimes we want to assign an issue to a dummy user, such as 'Dev Team', until someone from the dev team actually assigns the issue to themselves.
Or assign to a group.

The problem is that I cannot create such a user without paying for it in the cloud instance.

Also, we use Gitlab and we want Gitlab to integrate with Jira in such a way that when commits or merge requests are happening, we get a Jira comment added by Gitlab.

That was possible in the server instance, but again not in the cloud instance.

Is there a workaround for this issue?

Accepted answers

Jack Brickey

Create a “team” field with a single-select
leave “unassigned” to equate to triage
setup filters and dashboard if desired or even Kanban per team that leverages the team field

All comments

Jack Brickey

Create a “team” field with a single-select
leave “unassigned” to equate to triage
setup filters and dashboard if desired or even Kanban per team that leverages the team field

John Funk

I second this as that's the solution we have used in a couple of projects.

Gil_2dvf2c

@Jack Brickey thanks for the suggestion.

If using the custom field, are you able to incorporate it into your workflow?

i.e. - as a post function, to assign to someone/group?

It's an interesting solution though

Jack Brickey

@Gil , you can use the custom field in a PF however, you can’t assign to a “group”. My intention here was to use unassigned as the triage queue and the teams would monitor and keep that list empty by assigning each issue to a single user and/or set the Team custom field to the appropriate team. If the Team field is set and the issue is unassigned then it is up to the team to scrub their list and get it assigned.

Gil_2dvf2c

I'll just add that if someone doesn't want to create a custom field, then you can still:

invite a dummy user, i.e. developers@YourDomain.com
then in the Permission scheme of your project, add Assignable user permission to this dummy user.

Works as I need for my cause.

Thanks!

Salomon

Seems to work!

I did it like this: I created a group where I assigned all department-dummy-users to. I ensured that these users are users of Jira Software but are only in that group (not the jira-software-users group).

I edited the permission scheme of my project (in my case the default permission scheme, because I want it for all projects like this) and granted access for the group for "Assignable User" permission.

In the billing section these users seem to be not counted!

Thanks for sharing

Ignas Selvestravičius

@Gil but in that way you still have to pay for that dummy user, right? The license is required for it?

Nic Brough -Adaptavist-

If you want to make any use of a dummy (like naming it in fields like assignee), you will need to licence the "user" as though they are a real person.

Gil_2dvf2c

@Ignas Selvestravičius that is correct.

It's something I wish Atlassian will provide some solution for in the future.

Rizwan Rizvi

@Salomon how id you provide access to jira software for the group?

I tried adding the group for product access but it automatically increases count of billable users.

Nic Brough -Adaptavist-

Yes, that's how it should (and does) work - you're adding a load of users to the system, and the licences are based on the number of users.

Salomon

@Rizwan Rizvi We only use these users for assignment. for nothing more. Example: we have a Code-Department user and an Art-Department user. We use them if it is not clear yet who of the respective department will do the task.

We also have a user for creating issues through a web hook ("Bug Reporter" user). That user is not free, unfortunately. I think it needs too many / too powerful permissions.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

account