Configure ‘Related Jira Issue’ component
- Add ‘Related Jira Issue’ component
- Configure ‘Related Jira Issue’ component
- Access Rights to Peeklogic JiraContent Component
- Create Jira Issue in existing tab (PRO)
- Create Jira Issue in new window (PRO)
- Associate/disassociate Jira Issue
- Create Sub Task
- Link Jira Issue
- Edit Jira Issue
- Transition Jira Issue + (workflow form)
- Create Service Request (PRO)
- Edit Service Request (PRO)
- Manage Watchers (PRO)
- How to setup Project and Issue Type as default when creating Issue (PRO)
- Ability to refresh Jira Issue on ‘Related Jira Issue’ view manually (PRO)
- Search and Link Jira Issue by Versions (PRO)
- Set Jira Statuses restriction (PRO)
Add ‘Related Jira Issue’ component
- Choose a Salesforce Record that you wish to connect with Jira Issues.
- Peeklogic Jira Connector enables the linking of Jira issues to diverse Standard or Custom Salesforce object records, such as Cases, Accounts, Opportunities, and others.
- Navigate to Setup and click ‘Edit Page’ to incorporate a JiraContent lightning component into the layout of any standard or custom object, enabling the linkage of Jira issues with Salesforce Records.
- Add JiraContent Lightning Component to the page.
- Adding JiraContent Lightning component will allow you to:
- Create Jira Issues from Salesforce;
- Add Comment, Attachment, Link Jira Issues within Salesforce;
- Flexible Search for Jira issues and link them to Salesforce Records (Salesforce Custom and Standard objects are supported).
- Click on ‘Create Jira Issue’ on JiraContent Lightning component to create Jira issue from Salesforce.
Configure ‘Related Jira Issue’ component
Clicking on ‘Related Jira Issues’ component you will see a list of features for configuration.
Access Rights to Peeklogic JiraContent Component
Peeklogic Jira connector allows the configuration of different access rights based on profiles and field values. You can configure to allow/not allow the following functionality in a flexible manner:
- Show/Hide Create Jira Issue button for different profiles and records;
- Show/Hide Search Jira Issue button;
- Show/Hide Create Sub Task button;
- Show/Hide Link Jira Issue button.
So for example – one profile can have permission to create a Jira Issue, another only to add comments.
Peeklogic Jira Connector allows it to be configured in Salesforce Lightning App Builder as per the following steps:
- Open a Salesforce Record where you’d like Peeklogic JiraContent Component to be visible.
- Click Edit Page to open Salesforce App Builder.
- Add few JiraContent Lightning Components to the Page and configure different visibility using Salesforce Set Component Visibility configuration for each JiraContent Component.
As a result, we can have one JiraContent Component with Create Jira Issue and Search Jira Issue buttons available for one Profile, and another JiraContent without buttons available for another Salesforce Profile.
Create Jira Issue in existing tab (PRO)
Create Jira Issue – Configure settings to include a ‘Create Jira Issue’ button, enabling the creation of a Jira Issue within the current tab.
Create Jira Issue in new window (PRO)
Open modal dialogs in a new window – Implement a feature allowing the creation of Jira Issues in a new window while displaying relevant information from Salesforce Records.
Associate/disassociate Jira Issue
Associate
Search Jira Issue – Enable the association of Jira Issues with Salesforce Records through two methods:
- Basic search by Issue Key or Summary. Click on ‘+’ to associate Jira Issue;
- Advanced search with various filters. Click on ‘+’ to associate Jira Issue.
Disassociate
Implement disassociation capabilities:
1. Remove the custom Permission Set from Profiles to unlink Jira Issues:
- Go to Profiles and select Profile you want to allow to unlink Jira Issue;
- Click on ‘Enabled custom Permissions’;
- Click on ‘Edit’;
- Move ‘Jira Connector.peeklogic_jc.Disable ‘Unlink Jira Issue’ Feature’ from ‘Enabled Custom Permissions’ column to ‘Available Custom Permissions’ column;
- Near each Jira Issue, an ‘x’ button will be visible. Upon clicking it, the Jira Issue will be unlinked from the Salesforce Record.
2. Utilize the ‘Search’ function to locate a Jira Issue by Key and unlink it:
- Find Jira Issue by Key and click on ‘✔’ button to unlink Jira Issue.
Create Sub Task
To find Sub Tasks and Linked Issued click on ‘View’ on linked Jira Issue.
Create Sub Task – Configure an option to add a ‘Create Sub-Task’ button for generating Sub-Tasks related to existing Jira Issues.
Link Jira Issue
Link Jira Issue – Implement an ‘Issue link’ button to establish links between Jira Issues.
Edit Jira Issue
Edit Jira Issue – Add an ‘Edit’ button, allowing users to directly modify Jira Issues within Salesforce.
Transition Jira Issue + (workflow form)
Transition Jira Issue + (Show a form on workflow transition) – Replicate the ‘Transition’ button to alter Jira statuses directly within Salesforce and use a workflow form.
Create Service Request (PRO)
Create Service Request – Enable a ‘Service Request’ button for creating Service Requests within the current tab.
Edit Service Request (PRO)
Edit Service Request – Implement an ‘Edit Service Request’ button to modify existing Service Requests.
Manage Watchers (PRO)
Introduce a feature similar to Jira’s ‘Manage Watchers’ for managing watchers within the Salesforce environment.
Jira Watchers is a feature in Jira that allows users to ‘watch’ specific issues. When a user watches an issue, they receive notifications about any changes or updates to that particular issue. This notification mechanism helps users stay informed about the progress and discussions related to the issues they are interested in. Watchers can include project team members, stakeholders, or anyone else who wants to stay updated on a particular issue’s status.
In order to use feature Watchers follow to ‘Edit Page’, click on the ‘Peeklogic JiraContent’ component and select ‘Manage Watchers’.
Let’s consider the possibilities of using Watchers directly in Salesforce:
- Add Jira Watchers during creating the new Jira Issue by using the button with an eye icon;
- Review Jira Watchers during viewing of the Jira Issue by using the same button;
- Add Jira user as new Jira Watcher by starting typing the first letter of name;
- Remove Jira user from list of Watchers by cross icon.
In the event that a Salesforce user does not have a corresponding user in Jira, it can be mapped to another Jira user. Furthermore, Salesforce users can be mapped to the relevant Jira users directly within the Peeklogic Setup for both manual and automatic creation of Jira Issues.
How to setup Project and Issue Type as default when creating Issue (PRO)
– Navigate to ‘Peeklogic Jira Projects’ and ‘Peeklogic Issue Types’.
- Choose the desired Jira Project you want to set as default when creating a Jira Issue.
Check the checkbox labeled ‘Set as default for issue create’.
- Once configured, the selection of Project and Issue Type will be omitted when initiating the creation of a new Jira Issue, utilizing the defaults you’ve set.
Ability to refresh Jira Issue on ‘Related Jira Issue’ view manually (PRO)
Ability to refresh Jira Issue on the ‘Related Jira Issue’ view manually without refreshing the entire Salesforce record screen
Search and Link Jira Issue by Versions (PRO)
Firstly, button should be added to the Peeklogic JiraContent component. Follow to Lightning App Builder and enable the ‘Search Jira Issue By Version Button’ checkbox in the Peeklogic JiraContent component.
Now the ‘Search By Version’ button is available for using.
Select Jira Project and one or more necessary Versions for searching Jira Issues.
The necessary Jira Issues can be linked separately via the ‘+’ icon or all found Jira Issues via the ‘Link All Issues’ button.
Setting Jira Status Restriction for ‘Related Jira Issue’ Component (PRO)
Make sure you have Jira Connector version 1.308 or higher.
Restrict Salesforce users from transitioning Jira issues unless they meet specific criteria, using the ‘Related Jira Issue’ component in Salesforce powered by Peeklogic Jira Integration.
1. Navigate to the correct Peeklogic Jira Project record in Salesforce.
2. Get the required Jira transition IDs from Jira.
3. Populate the peeklogic_jc__Restrict_Issue_Transitions__c field with JSON
| { “user”: {}, “profile”: {}, “global”: [ “61”,”81″ ] } |
Where Global contains Jira transition IDs.
Note: only Statuses you added to peeklogic_jc__Restrict_Issue_Transitions__c will be visible on the ‘Related Jira Issue’ component in Salesforce.
4. Save and test the restriction in the ‘Related Jira Issue’ component.