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; } } }

Need to Tag Issue to Component based on Board

Shrikant Bijapurkar _NTT DATA_

My project has 2 Boards A and B

When an Issue is created on Board A, I want to set the Component/s field to "Comp A".

When an Issue is created on Board B, I want to set the Component/s field to "Comp B".

Above can be achieved via automation by putting If - Else condition on Board name.

But it seems it is impossible to use Board name in JQL.

Is there any alternate way to fulfill this requirement?

Accepted answers

Alex Koxaras -Relational-

Hi @Shrikant Bijapurkar _NTT DATA_

Every board has behind it a JQL. So instead of trying to use the board in your JQL, use the whole board filter on your JQL (ref: here and here).

I mean, what is the main differentiating reason behind board A and B? Use this to set the components via automation.

All comments

Alex Koxaras -Relational-

Hi @Shrikant Bijapurkar _NTT DATA_

Every board has behind it a JQL. So instead of trying to use the board in your JQL, use the whole board filter on your JQL (ref: here and here).

I mean, what is the main differentiating reason behind board A and B? Use this to set the components via automation.

Shrikant Bijapurkar _NTT DATA_

Thanks Alex.

That makes sense and I tried doing the same when I started on this requirement.

The need is to set the Component/s field to Comp A, "at the time of creating Issue".
The Board filter on Board A shows all Issues that have "Comp A" component.

So, its Chicken and Egg. Board A query cannot find the Issue since "Comp A" is not set AND its not possible to set "Comp A" since its not possible to know the Board on which it is created.

Here is the actual Board Filter Query:
project = SPL AND issuetype != "Risk&Issue" AND component in ("Software SDK") ORDER BY Rank ASC

The need is to set value of Issue's Component/s field to "Software SDK", when its created on "Software SDK" board. We want to have a If Else in Automation to allow doing the same for another Board on the project "Core Toolchains".

"Software SDK" and "Core Toolchains" are Components on SPL project (pls see the attached).

Any guidance would be greatly appreciated.
I hope I have been able to articulate the requirement clearly.

Alex Koxaras -Relational-

Thank you for the clarification @Shrikant Bijapurkar _NTT DATA_ !

From the image you pasted, it looks that you are on jira server/DC (on premise) and not on cloud as you initially posted on this question. This makes things a bit easier

In order to achieve what you want you have to first identify when an issue is going to be placed on board A. And the answer to that, is NOT "when it will have the comp A". You need a business requirement for that.E.g.:

"Issues of type "risk" or "bug" must have component A, thus they will be appearing in board A.

On the other hand, issues of type task, subtask and story, should have component B and thus they will be visible only on board B"

Once you get this, you can create your If/then/else automation and either use:

Jira automation to place the appropriate component value
A post function within your workflows to set the component value
Scriptrunner's behavior to change from the create screen the value of the component and make it read only

But in order to make any of the above solution, you need to clarify with your company/boss/colleagues the main differentiating reasons of when an issue is going to have comp A value and when comp B value.

Hope that makes sense

Shrikant Bijapurkar _NTT DATA_

And here is the Query Filter for "Core Toolchains" Board -

project = SPL AND component in ("Core Toolchain") AND (issuetype = Epic AND (labels != tech-debt OR labels is EMPTY) OR issuetype in (Story, Task, Sub-task, Bug, "Risk&Issue")) ORDER BY Rank ASC

As with "Software SDK" the need is to set the value of Component/s field to "Core Toolchain" when the Issue is raised on Core Toolchain Board.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud