Creating issue in scrum board isn't auto-populating component

[Graciela Ruiz]

In most scrum boards, when I create issues in the backlog/plan tab, the component field will auto-populate in the issue so it falls into board's filter.

I am currently getting the message "Your issue XXX has been created but is not currently visible." This is because the component my board is filtering for is not being auto-generated in the task (like the epic and sprint fields).

This doesn't happen on other boards and seem to have the exact same configuration. 

[Brittany Wispell]

Hey @Graciela Ruiz

How is the component field being auto populated?

Have you checked the workflow post fucntions configurations? 

[Graciela Ruiz]

So I have two boards that are just filtering Project and Component

For Example, 
Scrum Board 1 is filtering project Apple and component A

Scrum Board 2 is filtering project Apple and component B


within Board 1, I can add issues to the backlog and newly created issues will be created with component A added automatically.

In board 2, when I add issues to the backlog the component is not added automatically.

[Graciela Ruiz]

I thought it was just a feature in Jira that when you create issues directly in the scrum board, it auto fills the sprint field, epic, field and other values to try to keep it within your boards filter query. 

It's odd because if I edit the filter to a different component, the field will auto-populate. It's just certain components that it doesn't work with. 

[Graciela Ruiz]

So I literally edited the exisiting component name suddenly the auto-populating worked again. It just doesn't like the original component name. I wonder if there's like Jira cache that I need to clear. 

[Brittany Wispell]

Hey @Graciela Ruiz

Could you show me the issue you were having? 

I'm curious if it was a workflow post function or something else. 

Usually when things are auto populated it's something in the workflow. 

But if you are talking about the drop down list of options for component/s, that's something different all together. 

I'm glad it is working now! 

[Piyush_Annadate]

Same is happening for me - is there a bug ID already opened for this?

[Evangelos Vrocharis]

Yes here's what's causing this :  https://jira.atlassian.com/browse/JSWSERVER-14728 

[Benoit Beaulieu]

Well we don't have the issue yet because we are setup our Jira in a small team now, but it is definitaly a need that we have to expand the usage of Jira in the company. +1 to being able to use the same component and populated it automatically even if it exist in different projetcts.