Bruno Altenhofen Atlassian Team

Discussions

    • Automatically link tickets by a issue comment

      This workaround is meant to help JSM, JSW and JWM projects where it is necessary to link Issues mentioned in a comment. At the moment, this functionality isn't available natively in Jira, we have a request feature created for this topic: * JRACLOUD-46065 - Link Issues mentioned a ticker id Workaround steps: * Automation…

    • Copy a Form to the same project and for different projects using Automation and API

      As an extra option of workaround to the feature request "Include Forms when cloning an issue", this guide is designed to assist users in using the Forms API to automatically duplicate a form between issues. Steps to Follow: * Set Up an Automation Rule:* Create an API token for the web request process. This requires…

    • Automatically update Form fields answers and manipulate more than one form on an issue

       Deprecation Notice: Removing access to Forms data using Jira entity properties API To access forms properties after the deprecation, it will be necessary to use the new feature for Forms smart-values: * Manipulate Access smart values for forms and form fields Alternatively, you can access these properties via the Jira…

    • Using Cascading Fields with Forms and Assets

      This workaround is meant to help users that want to use cascading fields with forms or use a 3+ level cascading custom field type. So this is an option of the workaround from the features below: * JSDCLOUD-10792 * JRACLOUD-7936 And is meant to help projects where it is necessary to use multiple select options in a field, I…

    • Add an approval step using Jira Software and Work Management

      This workaround is designed to assist Jira Software (JSW) and Jira Work Management (JWM) projects requiring an approval step in the workflow. Before we start, allow me to share that Jira Service Management (JMS), offers a unique feature of approval steps that isn't available in other Jira products like JSW or JWM. The…

    • Submitting or reopening a Form using Automation and REST API

      This guide is designed to assist users in utilizing the Forms API to automatically submit or reopen forms. If you need to handle multiple forms, please refer to the following article: * Automatically Update Form Fields and Handle Multiple Forms Steps to Follow: * Set Up an Automation Rule:* Create an API token for the web…

    • A helpful guide to export issues only with public comments

      This workaround is intended to support Jira Service Management (JSM) projects that require exporting issues with only public comments, excluding internal ones. Currently, there are limitations in JQL's ability to differentiate between public and internal comments. Since JSM is primarily designed for customer interaction,…

    • Automatically send all the issue public comments by email

      This workaround aims to assist Jira Service Management (JSM) projects (can also work for JSW and JWM products), which involves utilizing the Automation for Jira (A4J) feature to share all public (customer-visible) comments made in a issue via email. This design is particularly useful in scenarios where you want to generate…

    • Can fields in a form be searched using a JQL query?

      This workaround is meant to help projects where it is necessary to run JQL queries for the fields related to the form. At the moment, unless we map every Forms field to a Jira field, they will not be searchable through the JQL query, we have a request feature created for this topic: * JSDCLOUD-10507 - JQL search/basic…

    • Using Forms Smart Values

      This article is designed to assist users in utilizing the new Forms Smart Values. With these, you can now manipulate form information effectively using smart values. For more information, please refer to the features below: * JSDCLOUD-10697 - Forms Automation: Access form fields with smart values (smartvalues) These smart…

    • Reading a Forms(Proforma) field value without the JSON tab

      Important Notice: This documentation is no longer functional due to the deprecation of Forms Properties. For more information, please see the Atlassian Changelog. To access forms properties after this deprecation, please use the new Forms Smart-Values feature: * Manipulate Access Smart Values for Forms and Form Fields 📘…

    • A helpful guide to creating organizations in bulk

      This workaround is designed to assist Jira Service Management (JSM) projects in exporting new organizations in bulk. At present, there are limitations, as creating multiple organizations in JSM via the REST API requires sending individual POST requests for each organization. The JSM Cloud REST API does not currently…

    • A helpful guide to automate comment copying across JSM, JSW, and JWM projects

      This workaround aims to assist Jira Software (JSW) and Jira Work Management (JWM) projects that require communication with Jira Service Management (JSM) projects, which involves utilizing the Automation for Jira (A4J) feature to copy comments made between these projects. At the moment, there are certain limitations in how…

    • Populate a user picker field from the description field

      This workaround is meant to help JSM projects where it is necessary to pull someone mentioned in a text format from the description field into a user picker field, like the Reporter field. At the moment, the lookup of a user picker field is by ID and not text. Therefore, the A4J will not be able to add the user account and…

    • How to parse the description field for values to put into other Jira Custom fields

      This workaround is meant to help projects where it is necessary to get information from an email request's description field and enter it into specific Jira Custom fields. This saves time in a daily routine by not having to enter the values manually. For this, we can utilize Automation For Jira (A4J) with some Jira Custom…

    • Change Form visibility using Automation and API

      Work has already started on the new Forms API functionality and we now have some experimental APIs available for use. So now Marketplace Partners can already integrate forms into their products. For more information, please refer to the features below: * JSDCLOUD-10671 - REST API for ProForma/Forms in Jira As a workaround…

    • How to change a form date field format and convert the time zone

      This article is meant to help projects where it is necessary to change the date & time format from a Jira field or Form field. At the moment the Forms date format is not the same as Jira date format as the Forms date format will be always "dd/MM/yyyy" or "MM/dd/yyyy" and not other formats. We have a bug ticket that was…

    • Add predefined values and create a Calculation Form with Assets

      Following the same logic from 'Create a Calculating Form' which explains how to calculate form number fields and make the sum of the values at the end, here I'll explain how to calculate fields with a predefined value and leave a total value. So this is an option of the workaround from the features below: * JRACLOUD-61966…

    • Add a Form using Automation and API

      Work has already started on the new Forms API functionality and we now have some experimental APIs available for use. So now Marketplace Partners can already integrate forms into their products. For more information, please refer to the features below: * JSDCLOUD-10671 - REST API for ProForma/Forms in Jira As an extra…

    • Create a Calculating Form

      Different from 'Add Issue Score for Jira by calculating choice fields' which explains how to calculate text and choices fields and add a score at the end, here I explain how to calculate number fields and leave a total value. So this is an option of the workaround from the feature JRACLOUD-61966 and is meant to help…

    • How to set up a issue security on a request type basis

      This workaround is meant to help company-managed projects where it is necessary to block the view of a request type and, for information security reasons, make it visible only to the reporter and a specific agent. At the moment, the security level is only able to be set to Issue Type and not for a Request Type, we have a…

    • Assign a new ticket to a specific agent based on values choose in the issue fields

      This workaround is meant to help projects where it is necessary to assign a new issue/request directly to a specific agent to better organize the queue management. For a such scenario, I used ProForma with Automation For Jira(A4J). Also, I used as an example a form related to an IT - Change request, where the customer will…

    • Avoiding duplicate forms when using ProForma and JSM Forms

      This workaround is meant to help JSM customers/users that have projects that already have ProForma activated but would like to use JSM Forms instead. For such scenario, I already have ProForma activated in a JSM project but I would like to use JSM Forms. If I have both installed I will be facing an expected behavior which…

    • Change the Summary based on values filled in the issue fields

      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…

    • Add Issue Score for Jira by calculating choice fields

      This workaround is meant to help projects where it is necessary to calculate text fields linked to numeric variables for the sum of a score. In this documentation, I used ProForma with Automation For Jira(A4J). Also, I used as an example a form related to a questionnaire on basic health care and in which it calculates a…

Avatar