How to identify one board from another within a project for automation rules?

[Scot McGavin]

I have multiple boards within a project (space) for different teams.  Each has their own board.  When creating new work items, I want a field like component or category to autopopulate uniquely for the right team based on the board they are on when creating the item.

I have tried to set up Component to do this and it does not work according to the Atlassian documentation (Pre-populate the Component/s field while creating an issue from the Board View. | Jira and Jira Service Management | Atlassian Support) so I am trying to use an automation rule, but I don't see any way to identify a board as part of the scope for the rule.  I can identify the project (space), but not which board within that space.

We are using Jira Software Cloud and currently are doing a trial of Premium.

[John Funk]

Hi Scot - Welcome to the Atlassian Community!

The board is just a view of selected work items in your Jira instance. So, there is not a way to say this one done on this board or that board. However, each board has a specific filter used to determine which cards show on which boards. Therefore, that's what you would use to most likely determine "which board" it was on - it would be a series of Conditions in the automation rule. 

I hope that helps get you on a path to a solution. Feel free to ask more questions for clarification. 

[Trudy Claspill]

Hello @Scot McGavin 

Welcome to the Atlassian community.

What are the filters used by each team's board? What are the fields and their values used in those filters to distinguish that an issue should be displayed in one board vs. another?

I note that the article you referenced says that it applies only to Jira Data Center while the tags on your post say you are using Jira Cloud. Here is the Jira Cloud version of the KB:

https://support.atlassian.com/jira/kb/auto-population-of-component-value-during-issue-creation-in-jira-software-boards/

Do note that the auto-populating of Component works only when only one Component value is included in the board filter, and per the article the work item has to be created from the backlog, not from the board.