Jira or ScriptRunner Automation w/ User Inputs

[Jack D_ Leach]

Hi all - I'm looking to fire off some automation associated with an issue (e.g., from a button or Automation link on the card) that is capable of taking some user input.

I envision a modal form that I could collect a few values from the user then continue the automation.

I'm open to using either Jira Automation or ScriptRunner, but hoping to keep it relatively low-to-no code (we're a dev shop and can handle it, but trying to avoid the learning curve for a quick implementation).

I've done some searching and can find peripheral info on Forms, but it's not clear if I can use them for this purpose.  Most attempts bring up Smart Fields, which are only capable of reading from previously existing fields. 

As a workaround I could add these user parameters as fields in the prior screen, but they're really not strictly necessary to the parent ticket so would prefer to omit.

Any ideas?  Thanks! 

[PD Sheehan]

Granted, I'm not that experienced with Automation, but I don't think it has any form/input capabilities.

Short of some other plugin, your choice for collecting user inputs are:

1) a jira screen with custom fields. Use a "Any Status to Itself" transition and link your screen as a means to trigger the action. All your actions can then be added to the workflow post-function including triggering an automation rule.

2) Use scriptrunner to create a custom dialog, and trigger either a native or custom rest endpoint from the form. This will require a custom REST api to generate the form. A fragment to expose a menu item to open the form. Some javascript to react to user input in the form including a call to the rest api on submission.

[Jack D_ Leach]

Thanks @PD Sheehan these are good ideas.

We've decided on building a few custom frontend dashboards in-house and using the basic Jira REST apis to invoke the work.  The fragmentation of actions, logic and trigger points throughout the native (+scriptrunner) environment is far too fickle to build complex business logic with any degree of control, and incidentally that's what our company does anyway, so it's a fairly light project.  It'll take longer to work up, but once done everything lives in one place under our direct control with the only 3rd party requirement being Jira's API itself, which is solid enough for me.

[PD Sheehan]

Oops, I missed the "cloud" tag. 

My Suggestion may not work on cloud. My experience is mostly on server.

[Rafael Costa]

Hi, @Jack D_ Leach .

This automation will trigger something like a transition screen but instead would be a button/link, right?

[Jack D_ Leach]

Hi @Rafael Costa - it will trigger many things, for example:

Intake Issue to have a "Create Patch" action that will do the following:

* Create a patch type issue
* Create a work order issue to file the patch under
* Create a dedicated release issue, if specified by the user, and link the work order and patch card to it
* Carry over priorities from the parent intake issue to each sub-process issue
* Trigger transition of intake card to completed status

Essentially it's the user invoking a standard workflow that could have long arms and deep roots.

Thanks