We have several teams all sharing the same project. Each team has its own board, with a custom filter to only surface tickets relevant to that team based on a component.
I would like to create an automation flow where I can add a specific component based on which board the Create issue button is selected. Alternatively using the url would also work.
Is there a way to do this?
Hi @Cary Lewis
Maybe...but not as how you describe it...
A board is a view of issues in a project based upon a filter. Automation rules cannot know about the "board" but you could determine if an issue matches a filter for a particular board, and take actions as needed.
IMHO: this is a risky rule unless your rule specifically uses the saved filter ids to confirm the board filters stay in synch with your rule logic.
Kind regards,
Bill
Hi @Cary Lewis
I would do it like this....not perfect, but easy enough automation to write.
trigger = issue created
Condition = If/else block
Where if reporter is one of [Insert all team members for the relevant team/component]
Action: Edit issue to add the relevant team/component
Repeat for each team.
Yes!! the downside is, every time there is a team member change the rule needs editing.
Plus, the teams need to be appear this is occurring and if they want to create for another team they will need to add or edit the component field.
Bonus idea; You could add an initial (pre If/else) condition of "If Component is empty" so that if they configure it at creation. the rule will leave it alone.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We had considered this approach, but in reality anyone on one team could create a ticket for another team, so this doesn't solve the problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.