Tasks created on board no longer inherit Component from board JQL filter after recent Jira update

Question

Previously, I set up multiple boards within a single project, where each board was filtered by a specific component so that newly created issues would automatically inherit that component. However, following a recent Jira update, this functionality no longer works—components are no longer automatically assigned when creating tasks or epics directly on the board.

Josh · Answer

Hi, adding to Viswanathan's reply. Atlassian documents exactly when this is supposed to happen (Auto-population of Component value during issue creation in boards): the component is filled in only for inline create on the board or backlog, and only when the board filter has a single component value. That gives you three things to check before calling it a regression: * Where you create from. Only the inline + Create in a board column or at the bottom of the backlog inherits from the filter. The global + Create button in the top bar never did. If the recent update changed which button your team uses (or the inline entry now opens the full create dialog for you), that alone explains it. * How the component is written in the filter. component = 10234 (the ID) is the safest form. With a name, e.g. component = "Payments", a component with the same name in another project can make creation fail or skip the value (JRACLOUD-96928). You can get the IDs from https:///rest/api/3/project//components in your browser. * Only one value. component in (A, B), or a component clause combined with OR, stops auto-population by design. If all three are fine (inline create, a single component by ID) and the field still comes up empty, that's a genuine regression and worth a support ticket with one board as an example. Until then, the automation Viswanathan described works as a backstop. Just keep in mind that a rule can't tell which board an item was created from, so each rule needs its own condition (work type, reporter, a label) that decides which component to set.

Viswanathan Ramachandran · Answer

Hi,

Welcome to the community.

Hows your JQL filter look like? Does it include single component only or using multiple clauses? The filter assignment works on single component. Plus, if your component is spread across multiple projects, it will break. See

https://jira.atlassian.com/browse/JRACLOUD-89938

You can try setting up automation as below

* Trigger: Issue Created
* Condition: Issue Type is in (Task, Story, Epic) AND Component is empty
* Action: Edit issue -> Set Component to target value.