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

How to make "Assignee" field mandatory everywhere but the Backlog

Michel Mathia

Hello,

I would like to have the assignee field mandatory (i.e. issue not unassigned) in all status of the issue, but just not in the backlog. In backlog, we still don't know who will work on it, so we allow an issue to be unassigned.

I could (and I did) set a validator in the transitions to ensure there's an assignee during transition leaving the backlog, but nothing prevents to unassign afterward.

Thanks for your hints.

Michel

Accepted answers

All comments

shetty

Hi Michel,

set only assignee condition in the transition, then only assignee can execute transition and most important click publish draft else changes won't effect

Michel Mathia

Hi Ramesh,

Thanks for the idea.

But when the issues are in the backlog (potentially unassigned), the manager set an assignee, and the manager change the status to "selected for development" (or whatever status comes after the backlog).

Wouldn't this prevent the manager to change the status after he assigned the issue to a team member? (because the manager is not the assignee)

Also after the transition, does it prevent to change to "unassigned" without changing the status (i.e. without transition)?

shetty

-yes it will prevent the manager to change the status once you have updated the transition with only assignee condition

-no,you can change assignee at any time

Michel Mathia

Unfortunately, I what the manager to be able to change the status even when he's not assignee.

Also, when the status is not "Backlog" I want to forbid the possibility to unassigned the issue.

Milan Chheda [INFOSYSTA]

There is an administrative setting for making Assignee as mandatory at:

Administration > System > General Configuration

Search for "Allow Unassigned Issues" and turn it OFF. This would enforce and ensure that every issue created has an 'Assignee'.

But that would mean, an assigned issue in Backlog. May be, you need to introduce a status 'Not ready' between 'Backlog' and 'Selected for Development' OR when the manager moves the ticket to 'Selected for Development', have a transition screen that shows and allows for changing 'Assignee' field.

Michel Mathia

Thanks for the idea.

I know "allow unassigned issues" parameter, but it's not what I want.

The rest of the proposal still doesn't forbid to unassigned an issue that was assigned.

Kamel Meftah_ni7grf

Hey Michel, I know the topic is probably old, but if you are still interested about a way to deal with your request, I created a blog post about it "how to make the assignee field required in Jira"

Dina El-Mowafy

I liked the idea of adding assignee as required field on creation validators

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-core

jira-core-cloud