Better management of SLAs in Jira Service Desk; Better support for creating sub-tasks with required fields; Else / If has shipped; How to integrate Jira and GitHub using Automation for Jira; How to use Automation for Jira sample rules in your project; How to use Slack Messages with Automation for Jira; New String and Date functions inHi @Salih Zengin , welcome to the Atlassian Community. You can try to accomplish that with Jira Automation: Create an automation rule. Add a condition that it only applies to the cases you want. Add an „edit issue“ action and update the summary accordingly. You might want to use smart values for this. I am building a solution to use Assets for software asset management. My idea: Whenever a new software got approved in a Jira issue, the automation should create an object in Assets to update my software catalogue. Attributes should be filled with information available in the Jira issue (custom fields & fields in forms).
Use an appropriate Proforma smart value, for example for a text field, use: {{issue.properties."proforma.forms.i1".state.answers.AAA.text}} AAA is the Question ID, which you want to locate. To check each question, to verify which ID relates to which, create a smart value line for the number of questions you have - so I had 15 on my form, thus
I created the automation for when an issue is created to update the summary: To append more text, you must use { {issue.summary}} that will keep the current summary and then add the text you need. I used the Automation Lite that is a free app, but it only runs 300 automation per month, but they have another version where is not limitedWhen you build rules that create an issue in Jira Software you can use smart values to add Confluence information to the details of your ticket. Some smart values that might come in handy: {{space.name}} – the name of the space {{space.url}} – the URL link to the Overview of a specific space {{page.url}} – the URL link to a specific page
Navigate to the field value you want to display in your rule and click on the field. Then copy the ‘dot notation’ in the footer: In this example, the priority field is selected, which means the smart value is { {issue.fields.priority.name}} however, the fields section is not required so you could just use { {issue.priority.name}} or shorten