Is there any option to populate the component based on the Board where it was created?

[Mariia]

Hello community!

Need your advice. 
We have created a few components and boards that show issues with the corresponding component. (ex: Component 1 => Board 1, Component 2 => Board 2....)
Is there any option, when we create a new issue under this board to populate component for this issue automatically? (Issue created on board 2 should have components set to Component 2)

Thank you in advance

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

There is a slight problem with this idea.  Boards are not containers of issues, they are a view of a selection.  There is no "created in this board", it's actually "created and happens to match the definition of this board". 

You can create issues from the link to do it in a board where Jira will warn you "issue created, but this board doesn't select it, so you can't see it here"

This means two things to you

• Issues created "from a board" may appear on other boards.  You can't know which board the user was on when they clicked "create" (or if they used another Create link outside a board!)
• You can mimic "created on board so set component" with what @John Funk said!

[John Funk]

Hi Marlia - Welcome to the Atlassian Community!

Sure you can do that. The trick is that boards are actually based on filters - so you can create an automation that uses conditions based on the filter of your board. So this assumes that each board has a different filter or something like that which makes them unique. 

How many boards do you have? And can you share the filters from each? You can make them generic if you need to for data privacy - meaning project = ABC instead of actual name if you want. 

[Mariia]

Hi John! Thank you, happy to hear that it's possible!
So, the example of a board filter:
project = ABC AND component = "Component 1" ORDER BY Rank ASC
and let's say we have 10 boards (from Component 1 to Component 10)

What automation rules can I use?

[John Funk]

Well, there is nothing there that differentiates creating an issue between any of your boards. Which will make it impossible for it to know when board you were on as @Nic Brough -Adaptavist- says. 

So the only other thing I can think of is to add a new custom field with a dropdown of values related to the Components and make the field mandatory for your Create screen (you would actually do that in the Field Configuration for the project). Then you can use automation to copy the value to the Components field, or just change your board filter to use the new field instead of the Components field. 

[Mariia]

Thank you John.... I was thinking probably it can be somewhere in the board settings or something like this (kind of default values for issues created from this view).

Could you please explain what is the reason to use an additional field instead of Component? Can't we make the Component field mandatory in such case?

[John Funk]

Yes, you can certainly make the component field mandatory - that would be the more straightway approach. I thought you were trying to use other terminology than component for them. But definitely go with that.