Default to components when creating an issue

[Matt Marchesano]

Hello Jira Community,

We are using components to filter work for each team within a single project. A project will have multiple boards (1 for each team) and we are currently filtering each board by a component. When creating an issue, I was trying to see how I can default the issue component value to be the same one used in the board filter. I know creating an issue is by project so trying to find a clever way to set the default component value so that it displays in a specific boards backlog. Any ideas?

Thanks!

[Laurie Sciutti]

Hello @Matt Marchesano and welcome to the Community!  Are there other criteria used in the creation of new issues (i.e. Team) that you could use with an Automation Rule to assign the component?  If not, maybe a Scrum of Scrum to triage the new issues that you could then add Components?  Another idea might be to funnel submits through forms that you could then dictate how Components are added...

[Matt Marchesano]

Hello @Laurie Sciutti I am planning to make the component field required so that when issues are created, users can select the appropriate value. Thanks for the support. 

[sanam malleswari]

Hi @Matt Marchesano

Solution:

1. Automation Rule: Use Jira's automation rules to set the component based on the board.
2. Custom Field: Use a custom field to help identify which board the issue should belong to.

Steps:

1. Create a Custom Field: Create a custom field (e.g., "Team Board") that users can select when creating an issue.
2. Set Up Automation:
   • Go to Project Settings > Automation.
   • Create a new rule that triggers when an issue is created.
   • Add a condition to check the value of the custom field "Team Board".
   • Add an action to set the component based on the custom field value.

Example Automation Rule:

1. Trigger: Issue Created.
2. Condition: If "Team Board" is "Team A".
3. Action: Set Component to "Component A".

Repeat the condition and action for each team.

How It Works:

• When creating an issue, the user selects the "Team Board" value.
• The automation rule sets the component based on this value.
• The issue appears in the correct team's board backlog.
  
  

[Matt Marchesano]

Hello @sanam malleswari thanks for providing all this detail! Appreciate the support. I was going to see about setting the component field as required so that users must select the value before saving.