| templateType | template |
|---|
| templateOption | {"label":"FAQ Template Cloud Ready v2","value":"975385007470811129","templateType":"template"} |
|---|
| templateTypeOption | {"label":"Confluence template/blueprint","value":"template"} |
|---|
| templateId | 975385007470811129 |
|---|
| excerpt | Purpose To change a Jira issue's Assignee or Reporter, you are required to set the value mapping between the Jira User field and the Salesforce Case Owner. This documentation will help to provide an alternative workaround by using the Owner email address. Answer Configuration in Salesforce Go to Setup > Object Manager > search for the desired Object (e.g. Opportunity). Click to configure the Object, under Fields & Relationships , click New . Select Formula to capture the Case Owner's email address and click Next . Insert the Field Label and Field Name value. Then, choose the Text option. Click Next to proceed. Click the Insert Field button and design your field. Click Insert and press Next until you reach last page. Click Save to complete your custom field configuration. Confirm that the email address is now populated in the Salesforce Record. Configuration in Jira Create a Short Text custom field in Jira. In this example it is named "Jira User". Go to Apps > Salesforce > Bindings > select Mappings on an issue type and map the Jira field with the Salesforce field created. Save the configuration and confirm that the email address is populated in Jira when the data is pulled from Salesforce. Configuration in Jira Automation Select a project and navigate from Project Settings > Automation . Create a new rule with Trigger is Issue updated . Add a new component and select New Condition > Issue Fields Condition . Choose the Jira Field and set the condition as is not empty . Add another component and select New Action > Send Web Request Set the Web Request URL with the URL according to your Jira environment: Jira Cloud: <JiraBaseURL>/rest/api/3/user/search?query={{issue.<customField_Id>}} Jira Server: <JiraBaseURL>/rest/api/2/user/search?username={{issue.<customField_Id>}} To find the Custom Field ID, you can refer to How to find the id for custom field(s)? documentation. Before proceeding further, create an API token using a user that has the right permissions for the project based on the article below ( This step is not required for Jira Server & Data Center ): Manage API tokens for your Atlassian account Copy the API token and encode it with the username. You can use this third-party site to encode it. In the website's text box, arrange the username and the token in the following format: Jira Cloud: <username>:<APIToken> Jira Server: <username>:<password> Click Encode and copy the result back to the Jira Automation page. In the Headers section, set the name as Authorization . Set the Value with the following format, paste the encoded data from step 9 in the "<encodedToken>" portion of the text: Basic <encodedToken> Set the HTTP Method to GET and tick the Delay execution option. The configuration up to this point will look like the following: Click Validate your web request configuration and validate an issue from your project. The expected result is "HTTP 200 OK." Add the last component > New Action > Edit Issue. Do not select any field, instead expand the More Options section. In the text box, add the following: Jira Cloud: { "fields": { "reporter":{"id":"{{webhookResponse.body.accountid}}"} } } Jira Server: { "fields": { "reporter":{"name":"{{webhookResponse.body.name}}"} } } You can change the value between Assignee” or “Reporter” depending on your configuration. Save the automation and publish it. Related information Changing the Reporter and Assignee of an Issue |
|---|
| fieldGroupKeys | {"8gq4t5y21n":["net.customware.confluence.plugin.scaffolding__8gq4t5y21n__data_0_m6hf6k9l6i"]} |
|---|
|