Looking to have user be prompted with a list of choices which will trigger a rule

[Agustin Torero]

Hello ... looking to see if its possible.

Have user select a choice from a list presented when creating a story e.g.
Select A
Select B
Select C

Depending on the selection ... the corresponding Story Create Rule will run.
e.g. each of the three story rule has unique description (looking to load predefined information from templates e.g. business hypothesis, acceptance criteria, etc)

Thanks,

Agustin T.

[Zac]

Hi @Agustin Torero

Depending on how extensible these options need to be - perhaps it would make sense to have distinct issue types for each of the variations?

That way you could manage the fields natively via field contexts.

As @Valerie Knapp had suggested - another option would be to have a very minimalistic issue creation screen, with a simple custom field for each of your enumerations which drives automation-driven pre-population of fields.

Another approach would be to utilize workflows instead. You could have transitions to certain statuses that are only conditionally available based on the mentioned custom field value. The user could be presented with contextual custom fields to complete to progress the issue.

----

This likely isn't applicable for your use case given you've mentioned these are for stories - but another great option would be Forms and their powerful conditional visibility functions. These aren't available in Jira Software however.

In effect - these allow you to create dynamic issue creation screens. There's still a bit of work Atlassian needs to do to make the values provided in these forms easily accessible via Automation, but there's a good chance you wouldn't even need automation if you are able to dynamically show an issue creation screen :)

Thanks,

Zac

[Valerie Knapp]

Hi @Agustin Torero , thanks for your question.

This won't be possible with the standard automations included in Jira cloud, as there isn't a trigger that will allow you to amend the create screen / you could only modify an issue that was already created.

So, you could have a rule that, on issue creation for an issue type of story, if the story type (or another custom field you create) is A, then in the action, edit all of the fields you are want to populate, else if the value is B, edit the fields, else C and so on.

Within the create screen, you could try with Behaviours - Example Behaviour (adaptavist.com). I had success with using this in server. I know that the cloud potency isn't quite there yet but you could have a look.

I hope this helps.

Cheers

[Agustin Torero]

Thank you Valerie for your prompt response. I understand. :)

I will for sure make use of the 'manual trigger from issue' rule. And will look into the Behaviours information.

Thanks,

Agustin T.