autofill a customfield based on board query

[Amos Hoste]

Hi

I have an automation challenge I haven't found a solution to yet. I would like to automate filling in the Team of an issue based on the filter of the board that issue is created from.

We use the customfield Teams to filter boards for our development teams to look at relevant issues to them. The board filter could something like this: project = X and Team = A order by...

The Team field is a cusomfield, and I've identified the ID. But I do not know how to find the relevant value of team based which board the issue is created from.

Br Amos

[Trudy Claspill · Accepted solution]

Hello @Amos Hoste 

There is no way to automate setting the Teams field based on the board being viewed when the issue is created. While you can create an issue using buttons that display on boards, Jira does not track the board as the starting point for issue creation. Having the "Create" buttons available there is just a convenience.

[Amos Hoste]

Thank you for the answer @Trudy Claspill I suspected this to be the outcome. I've been going into the rabbit hole myself, and what I really need is the "This issue is not being displayed.. " thing to disappear. But from what I can find it's not possible because the Team field is a custom field that is not possible to set to a Global Context.

[Trudy Claspill]

Is there anything about the newly created issue besides the creation starting point that can be used to identify the Team that should be assigned?

If there is something, then that element could be used in an Automation Rule to set the Team field, I believe. That would happen after the issue was created so the message about the issue not being displayed would still occur initially.

[Amos Hoste]

Hi @Trudy 

Focus has been elsewhere, hence the late reply. I was hoping to be able to make a Global rule to "rule them all" but it doesn't seem to be possible.

Our alternative is to use the Team field from the Epic that the issues are associated to. But it will only work if the Epic has got the right Team chosen. And we might start out with having this to only run per Project as the Team field is not used consistently across our cloud instance.

Thank you for your thoughts.