Automation Service requests limited with Forms

[Deleted user]

I created a new Service requests that within it has a Forms, which was created to help when filling out, using Radio buttons and Checkboxes each one has a Field Key to identify them as well as a Display name.

When the Service requests ticket is created, the information is revealed in Attached forms.

Based on this new Service requests depending on the selection registered in the Radio buttons and Checkboxes I would like to create a new sub-task.

However, within the Automation option in the component (IF: Add a condition) it has the following components below:

{{smart values}} condition
Affected services condition
AQL condition
Forms attached
IF or ELSE: Add condition options
Issue attachments
Issue fields condition
JQL conditions
Related issues conditions
User condition

I would like to know if any of them is possible to use this function to read a keyword within the Attached forms or use the Field Key or Display name defined in the Form previously.

Example: If the Radio button is YES for "Will the user need a new Notebook?", below create a subtask for "Acquire new Notebook".

I have no problem creating subtasks, just finding where and how the condition option would be used.

Or could you tell me an alternative to carrying out this type of task.

Thank you in advance, thank you very much!

---

Criei um novo Service requests que dentro dele possui um Forms, onde foi criado para auxiliar na momento do preenchimento, utilizando Radio buttons e Checkboxes cada possui um Field Key para identifica-los assim como um Display name.

Quando criado o ticket Service requests as informações são reveladas em Attached forms.

Com base neste novo Service requests dependendo da seleção registrada no Radio buttons e Checkboxes gostaria de criar uma nova sub-task.

Porém dentro da opção de Automation no componente (IF: Add a condition) possui os seguintes componentes abaixo:

{{smart values}} condition
Affected services condition
AQL condition
Forms attached
IF or ELSE: Add condition options
Issue attachments
Issue fields condition
JQL condition
Related issues condition
User condition

Gostaria de saber se algum deles é possivel utilizar esta função de ler alguma palavra chave dentro do Attached forms ou utilizar o proprio Field Key ou Display name definido no Form anteriomente.

Exemplo: Se o Radio button for YES para "O usuário precisará de um novo Notebook?", abaixo criar uma subtask para "Adquirir novo Notebook".

Criação de subtasks não possuo problema, apenas para encontrar onde seria e como seria utilizado a opção de condição.

Ou poderia me informar uma alternativa para estar realizando este tipo de tarefa.

Agradeço desde já, muito obrigado!

[Marcus Jones · Accepted solution]

Hi @[deleted] ,

I'm not sure if it is possible at this time to pull field data from the form itself in that way. 

I believe you will need to create custom fields for the relevant form fields and link them. For example, one of your form fields is a radio button and we've named it "Client Type". "Client Type" has 3 options: "Prospect", "New", and "Renewal". We now need to go to our custom fields and create a new field called "Client Type" (Doesn't have to match your form field name but make sure you remember what you call it). For our new custom field we make it the type Radio Buttons and then set the options to match the form field options. Now back in our form field we simply link the form field to the custom field (Select your form field field and then go to "Linked Jira Field" on the right, find your custom field, and link them. 

Now that those are linked, in your automation you can use the values from your custom field/linked field in your IF statement to determine whether or not you need to create a sub-task. 

~Hope that helps

[Deleted user]

Hi, @Marcus Jones 

Firstly, I would like to thank you for your answer.

I chose Forms to get the answer due to a feature that I just found in Forms called 'section.' (I didn't find anything similar in the Custom fields to create and use it instead of forms to get data.) Using this feature, I can create a Radio button initially and check the condition if it's true or not. From there, I can show or hide this section. If shown, there will be more Radio buttons to collect essential data for the next steps.

A forum colleague sent me the option to using Jira API's ("Forms Automation: Access form fields with smart values (smartvalues)"); it might be beneficial for this case. I'll have a look at it.

Once again, thank you very much.

[Marcus Jones]

Certainly, glad I could help!