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

Do we have some ways to have Cascading component assigning default Assignee for the bug?

Hung Nguyen_dioizn

I know that we have Component today in JIRA, and by selecting Component, we can assign Component Owner to be Assignee.

In our organization, we need 2 levels of Component selection before an owner can be assigned:

- Let's call the first level is Module, one Module contains some Components or none. Module can have Module Owner, which if component is none, the module owner is used to be Assignee

- Level 2 is Component, each Component has a Component Owner, which when the component is selected, the component owner is set to Assignee

Is there any way to club the current Component in JIRA with another field (ie.Module) to do what we need above?

Thanks

Hung

Accepted answers

Joe Pitt

No, component is a single select and you'd have to do a major rewrite of code and commit to maintaining it. A work around would be to have another field the creator also selects so when the component owner gets the issue they would reassign it. You may be able to have a listener that looks at the second field after it is created and reassigns it. The drawback to that is you'd have to maintain the mapping of value to assignee.

All comments

Joe Pitt

Hung Nguyen_dioizn

When you said about "a listener that looks at the second field after it's created" do you mean some custom code to be written, or just some configurations we can do with JIRA ?

Joe Pitt

Custom code. I believe there is a plugin that allows listeners, but you'll need to write the listener. You can't do it with out of the box JIRA. We don't do anything that isn't supported by JIRA or one of the major plugins due to the hassle maintaining any modifications.