Get board ID

[Nouf]

Hello everyone, 

I want to compare the board ID using Advanced compare condition in automation rules because based on the board ID I will assign the team automatically to the issue created, so is it possible to get the board ID if jira is private if so how to do it?

[Nic Brough -Adaptavist-]

There's no point in doing this, the requirement doesn't make any sense.

A board is not a container for issues, it's a view of a selection of issues.  You don't create issues in a board, and issues don't have a "field" that says what boards they currently appear on.  Note the plural there - what boardS does the issue appear on after it is created?  Which of them would determine the team?

You should be looking at other data to determine what team the issue belongs to (not assigned to, as the assignee is the single person currently responsible for the issue)

[Chris Stein]

Wow, what a terrible answer to give someone!  Right up there with the infamous Steve Jobs response to users that they were "holding their phones the wrong way."

I'm trying to do something similar to what this requester is making and seeing this type of answer from a "community leader" is really off-putting.  In addition to being rude, you also make 2 completely incorrect statements in your response:

1. You don't create issues in a board - are you kidding???  There is a "create issue" link at the bottom of the backlog (& any unstarted sprint) on the backlog view of every board.
2. You should be looking at other data to determine what team the issue belongs to - again, are you kidding???  At this point in the creation process, all you have done is give the issue a title (the issue briefly appears at the bottom of the backlog and then disappears on the next refresh because it doesn't match the filters for the board) - there is no other data to determine what team the issue belongs to at this point.

Don't bother responding - I'll keep looking for a solution elsewhere - I just wanted to give some support for the poor person who made a reasonable request of the "community" and got such an un-helpful response.

[Nic Brough -Adaptavist-]

You won't find a "solution", you're looking for the wrong thing.  

1. As I said before, issues are not created in boards, but I could have explained that better.  The "create issue" link in a board is a convenience, not a "create in board".  It can't "create in a board" because boards are not issue containers.

2.  No, I'm not kidding, you need to think about the data you are entering that might determine the team.  Ideally, you've configured Jira to ask for the data that determines the team (even better if you can do it with a system field that is mandatory, like issue type or project)

[Chris Stein]

As I continued digging through the community discussions I do understand now that the concept of something like, "the board id that the user was using when the issue was created" is not a field on the issue itself and therefore not available to automations.  I understood from the outset that an issue isn't created on a board because we definitely show the same ticket on different boards depending on filter criteria.

In our environment, selection of a Team is a human decision which may be made at the time an issue is created but it is often a delayed decision (such as in bug triage).  The only time we have any kind of system information that would allow us to auto-select a Team is if the person creating the issue is looking at that Team's board and chooses to a create a new ticket in that context.  That's the problem I was hoping to solve.

[Nic Brough -Adaptavist-]

Yep, that's exactly it.  Atlassian actually expect a team:board equivalence, although they do not say it much until you get to using Jira Align.  Jira Align does not have a concept of a team as a separate item to board.  Every board in there is thought of as representing a team (anyone who can progress items across the board is part of the team)

The structure for Jira Software is a bit different, because although you can draw a team = board equivalence, it's easy to create boards that are not representing teams directly.  They're views of subsets of data that matter to the people using the board, which is not necessarily the team.  A lot of Jira users have many boards looking at similar arrays of issues for different non-team reasons.

A really simple implementation would be to have boards that have "team = X" for their board filter, but that needs you to have a team field, and for Atlassian to code for "when someone clicks create issue from a board, do not let them select a team, just set it to X".

It all comes back to the decision of how you're identifying teams.  Although there's an assumption of board = team, there's no code in Jira for it, mostly because it's very inflexible.