Is it possible to use "context" to display a trigger?

[Greg Zielinski]

Is it possible to use context or values in a request to display automation?  For example, I'd like an action "Push SQL Studio install" when SQL is mentioned in the request.  However, I do not want to list it if the issue has nothing to do with SQL.

Outside of "issues type", " assignee" and "issue status", is there any way to limit having all the automations I want to create from showing?  I'm just setting JSM up for the 1st time so I honestly can't say I know what this user interface will look like once I have 30+ automation to select from.  I suppose I could create an automation to take these types of requests and make a new "software install" issues type and then limit the automation.  That seems like I may be over engineering. 

[Christian]

Hi Greg

For manual trigger automations, right now the issue type is the only thing you can use to filter what automations are available, aside from the project itself. 

If you are concerned about potentially having lots of manual trigger automations available, I would advise you try to think about using other triggers. I don't know exactly what you are trying to achieve, but perhaps something like when issue is created and description contains "SQL", Push the SQL install. Or you could have it so whenever the "SQL" label is added this automation triggers. Again, I don't know the context of your configuration so these may not be useful. 

All the best,

Christian Veselovsky 

[Greg Zielinski]

The goal is a context aware menu of automations.

So we'd have a list of actions that can be trigged via something like SCCM.  But I don't want all 50+ options to appear.  I'd like "Push SQL Install" to appear as a trigger only if "SQL" is mentioned.  "Push Citrix Workspace update" would not appear in the manual triggers unless "Citrix" was mentioned.