nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can you set default values for fields on a Scrum Board based on the filters applied?

Loan Market JIRA Admin

I have a Scrum board that shows only stories that have a specific component. The board is configured to have a filter that is project = X and component IN (Y) Order By Rank.

When I create an issue through the quick add feature at the bottom of the backlog, it doesn't show on the board as the required component is yet to be added.

Is there anyway that it can be configured that when you create on a specific board, all new stories from that create view will include the specific component so they automatically show from day one?

Accepted answers

Jacob Wood

From what I know about JIRA, which board you are on has no bearing. Its the project you are currently in which dictates how the story is created. I would say the best way is to add the Component field on the create screen so the user is able to select the Component for each created story.

All comments

Jacob Wood

Loan Market JIRA Admin

Thanks for taking the time to respond!

I was playing around with it and you're right, the only way I could find to do it was make the field required in the field scheme and then it forces any new stories to be created with it.

Not the most ideal outcome but I guess it's a solution.

Jack Brickey

This is not possible, at least as you describe. Let me explain further. Issues do not belong to boards so are not ‘controlled’ by the board itself. You have a few options here and you should pick the one that results in less work or meets you desires.

leave it as is and change the component afterwords.
Force the default component to match the board and then change those that should not be there. Likely not a good plan unless other components are rare.
require the component at creation. This is, IMO, the best option.

there is one other possibility but rarely plays out well. If you can define some very unique rule that applies when creating an issue on this board then you could consider applying automation. For example, let’s say you only ever create issues for the project that apply to this board. If that were ALWAYS true then you could set the component based upon that fact. Likely untrue.

Loan Market JIRA Admin

Thanks for your response. I think I'm going to head with option 3. It's slightly limiting as it doesn't allow for rapid story creation when we're just trying to get the stories into the backlog for fleshing out in time, but I think it will solve for the more pressing need as detailed.

Dave Yost

For our configuration (and I don't know how specifically it was set up) - STORIES default to the SINGLE labels that are set for the board. So if my filter for the agile board is "and LABELS in (FRONT END) then when a story created ON THE BOARD the story has teh "FRONT END" label on it - YEAH

I am trying to figure out how to get EPICS to do the same thing - but don't think that is possible.

thib_d1lsk5

I had the same issue with my project and a dependency on the 'Team' field. When I clicked create, the issue wouldn't appear as the team field wouldn't be set.

My workaround was to include "parentEpic in" in my query so that, at least when the issue is created with the help of the epic panel, it gets auto-assigned an Epic, which lets the issue stay in the backlog view!

The only caveat is that the issue will not show up in the 'All issues' view when looking at the backlog. This might require some maintenance but it does the trick!

Hope this helps

project = FX AND ("Team[Team]" = 8 OR parentEpic in (FX-25,FX-7,FX-26,FX-27)) ORDER BY Rank ASC

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software