Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Release Version quick filter visible in Backlog but not on Board

Manpreet Arora
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 28, 2020

Hi,

On my Projects next-gen Jira board, I added Release Versions. After doing that, "Version" quick filter - with all the Release values - started appearing on the Backlog view automatically. PFA screenshot of the same << Filter_Visible_on_Backlog.png >>

Filter_Visible_on_ Backlog.png

However on the active Board, it's still showing only "Epic", "Label" and "Type" quick filters. The "Version" quick filter is not appearing. PFA screenshot of the same << Filter_not_visible_ on_Board.png >>

Filter_not_visible_ on_Board.png

Please let me know how to get the "Version" quick filter on the active Board - so that I can filter the User Stories - based on Fix Version / Release version, just like I am able to do on Backlog.

Thank you.

Kind Regards,

Manpreet Arora

6 answers

1 accepted

2 votes
Answer accepted
Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 1, 2013

Try this.

FieldConfigManager fieldConfigManager = ComponentAccessor.getComponent(FieldConfigManager.class)

0 votes
RambanamP
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 1, 2013

can you try with this

FieldConfigManager fieldConfigManager = ComponentAccessor.getOSGiComponentInstanceOfType(FieldConfigManager.class)

Ed Sattar
September 1, 2013

I tried ComponentAccessor.getComponentOfType same error

RambanamP
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 1, 2013

i have update my anser can you try with that!!

0 votes
Ed Sattar
September 1, 2013

import com.atlassian.jira.component.ComponentAccessor;

if (fieldConfigId != null)
{
FieldConfigManager fieldConfigManager = ComponentAccessor.getComponent(FieldConfigManager.class);
fieldConfig = fieldConfigManager.getFieldConfig(fieldConfigId);
}

0 votes
Ed Sattar
September 1, 2013

yes i am not injecting anywhere

0 votes
Ed Sattar
September 1, 2013

yes i am not injecting anywhere

0 votes
Ed Sattar
September 1, 2013

Now I am getting error

ComponentAccessor has not been initialised.

Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 1, 2013

You are writing a Java plugin, right? Are you sure you are not trying to inject ComponentAccessor anywhere?

RambanamP
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 1, 2013

can you share your code so we can check what is wrong!!

D. U.
Contributor
February 4, 2018

Doing it this way in my SpringBoot application I always get an exception that the ComponentAccessor is not initialized.

  

ComponentAccessor has not been initialised.

 

Can anybody tell me what I have to do that the ComponentAccessor will be properly initialized in a SpringBoot environment? Finally, I want to access the CustomFieldManager to work upon CustomFields...

 ...

customfieldMap.forEach((k, v) -> {
CustomFieldManager cfm = ComponentAccessor.getComponent(CustomFieldManager.class);
CustomField cf = cfm.getCustomFieldObjectByName(k);
System.out.println(cf.getValue((com.atlassian.jira.issue.Issue)v));
...
}
...

 

I get this exception even when I explicitely autowire the ComponentAccessor with 

 private ComponentAccessor componentAccessor;

public void setComponentAccessor(final ComponentAccessor componentAccessor) {
    this.componentAccessor = componentAccessor;
}

...but the ComponentAccessor should be accessed in a static way anyway, shouldn't it!?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events