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 enable changing the default assignee when the Component is changed?

Radhika Tk

Hi,

I have an issue screen, where i have made the Component field mandatory.

While creating the issue, the reporter , selects an appropriate Component value.

Now, the default assignee, realizes that this is not the correct Component and selects another value from the drop-down.

But the assignee is still the same. How to ensure that the issue is assigned automatically to the default assignee of the changed Component.

Thanks,

Radhika

Accepted answers

Thomas Schlegel

Hi @Radhika Tk,

an automatical assignment to the component lead only happens when the issue is created, not if the component is changed afterwards.

All comments

Thomas Schlegel

Hi @Radhika Tk,

an automatical assignment to the component lead only happens when the issue is created, not if the component is changed afterwards.

Vasiliy Zverev

There are two options:

Simple one, when you can define statuses where component change is allowed. In this case delete component from edit screen and create on each status a transition which starts and ends on this status. Add screen with component field and add biuld-in postfunction for assing.

Advantages:

no code is requared
spesial permission could be granted at each transition

Disadvatages: new transition is requares at each allowed status

Hard-code one: create a event listeres on issue update event and assing issue into it

Advantages:

could be pplied at any status of any workflow
the only one place for all usages

Disadvantages

need coding
dificalties with permission restrictions

Radhika Tk

thanks, i agree

Radhika Tk

thanks for your detailed explanation! I am sort of new to this and will take some time to get this in!