Change the Summary based on values filled in the issue fields

[#1]

This workaround is meant to help projects where it is necessary to change the contents of the summary field to better organize a project queue. For this, I used ProForma with Automation For Jira(A4J). Also, I used as an example a form related to a questionnaire of employment candidates, where it gets the candidate's name and the option selected. This method can be used for other purposes (eg. issues related to different company names).

Important related documentation:

Building Forms in ProForma
Working with Service Projects
Working with Software & Business Projects
ProForma & A4J
How AFJ works
Smart values

Workaround steps:

• Form settings:
  • It will be necessary to link the form fields that you would like to add the values to the Summary field to custom Jira fields (this is necessary for the A4J to be able to get the answers from the fields):
  • And it will be necessary to not lock the form on issue creation (this is important for having communication between ProForma and the A4J):

• A4J settings:
  • The best way to trigger this automation rule is by an 'Issue created' action, for another one it may not work as expected:
  • Specify which field the automation rule will work on:
  • Using Smart Values it’s possible to get the information selected by a customer in a field and paste it into the Summary field (also note the defined Re-fetch actions):
  • In the edit logs, I used three logs related to the select option of the section and the fields related to the candidate name:

    Qualification Verification for {{issue.customfield_10096}} {{issue.customfield_10097}}

    Onboarding Process for {{issue.customfield_10096}} {{issue.customfield_10097}}

    Career Development Planning for {{issue.customfield_10096}} {{issue.customfield_10097}}

    Note: To find the custom field ID please take a look at this documentation. Also, the text values can be changed for any value that you wish.

  • This workaround will work as shown in the screen recording below (note that it will always be necessary to refresh the page to give A4J enough time to execute the automation rule):