Installation and usage of Enhancer Plugin for JIRA

On this page, you can find documentation on installation, configuration and usage of Enhancer Plugin for JIRA.


Installation



  1. Download and install latest and applicable version for your JIRA
  2. See that you have plug-in installed in Administration -> Plugins page


  3. There are two ways two define JEP custom fields.
    You can either go to Admin > Add-ons > Enhancer Plugin > Custom Field Configuration page and define most of them easily.



    or define JEP custom fields by clicking "Add Custom Field" button under Admin > Issues > Custom Fields section.
    Just type 'JEP' under 'All' tab of custom fields list to see all JEP custom fields, click 'Next'.



    Set name/description and click 'Next'. Finally you will see screens list, select screen(s) that you want to see custom field. That's it.

    After adding custom fields, you will need to re-index by [Administration -> Indexing -> re-Index] in order to filter against these custom fields (reindexing is needed to filter for the issues before custom field creation).

You may wish to see custom field configuration section next.


Custom Field Configuration



Under Admin   Enhancer Plugin for JIRA   Custom Field Configuration menu you can define, delete or configure all JEP custom fields.

All custom fields can be configured by clicking gear icon at the right.

  • You can add and configure "Time Between" and response time custom fields under Time fields tab
  • You can add and configure "Time to SLA", "Overdue", "SLA Indicator" fields under SLA fields tab
  • You can add and configure "Date" fields under Date fields tab.
    There are built-in date custom fields, but you can also easily define your own status date field. Click "Add new Date custom field" link, and you will see necessary fields as below:

    If you want to define a custom date field for your status, just select "JEP - Custom Date", type a name for your custom field, and select the status you want to keep track the change date for.
    Finally there is a first/last occurence section. In some workflows issue may be in same status a couple times. In this case, issue may be in "Development" status twice but I need the last change.
    If you select "first", the custom field will show the first status change date in the issue history, and similar for "last".
    If you want to define built-in "Last Resolution Date" custom field, just select it, and type a name as below:
  • Very similar to "Date fields" tab, you can add and configure "User" related fields under User fields tab.
  • Like "Date" and "User" fields, you can add and configure counter custom fields under Counter fields tab.
    If you want to count how many times issue has been to a specific status and search against them, you can easily define counter custom fields.
    Similar to user/date fields you can define built-in or custom counter custom fields.


Features and samples


You can define your company's working calendar, and configure "Time" and "SLA" custom fields according to these working calendars

'Time Between' custom field

'Time Between' custom field calculates time passed between two statuses/events.
Tracking events feature is available since JEP 4.22.0 for JIRA 6.x or JEP 5.10.0 for JIRA 7.x

In issue main screen total working duration is seen and if clicked a dialog pops up





Time Between custom field can be configured from Admin > Add-ons > Enhancer Plugin Menu > Custom Field Configuration, and in the "Time" tab click on cog icon, then "Configure" or it can be created from scratch by clicking on "Add new Time Between custom field" link.



Time Between configuration page appears as below :



Name your custom field
Select the origin and target events, they can be any status or an event as 'Resolution', 'Reopening' regardless of status.
Calendar can be selected which is defined in 'Working calendars' menu item.
Occurrence type can be set to display only "First" or "Last" occurrence, or aggregated result with "Cumulative" option.
Time formatter is the option where duration string can be configured easily.

Paused (Frozen) statuses can be configured by clicking "Pauses" both in the cog icon, or in context configuration screen





There is a "Pause Options" button to add "Pause" statuses for "Time Between" custom fields. By adding any statuses, timer can be freezed.



Finally click Save button to see all in action.

In issue navigator :
Use Time Between searcher, and edit your interval as below


You will see the results as below :


You can define as many "Time Between" custom field as you wish.

Response time custom fields

Very handy custom fields that calculates the 'response' or 'no response' time. Responding to an issue is accounted by public comment. If the issue has been responded, response time custom field will be seen as :



If the issue is still waiting for a response, 'no response time' custom field will be seen as :



And the issue navigator :



Time tracker custom field

You can track time through all sub-tasks grouped by your JQL. For instance you may have an issue or story and you may want to calculate time passed through sub-tasks according to the issue types (development, analysis, test).
You can define as many group as you want by giving a JQL (e.g. 'issueype = Development) and the custom field will calculate not only the total time but also the time per user as below sample. Just click on group to drill down to user details.


SLA Configuration

Under admin   Add ons   Enhancer Plugin   SLA Configuration page, you can define as many SLA as you need.
Type the name (description) for the SLA, select priority, origin and target statuses. If you want SLA to take multi transitions into account (for instance Open to Resolved and in between there is "In Progress" status), check "Multiple transition?".
Here is a sample screenshot of SLA definitions.



You can add additional condition (using JQL) for the SLA. With Pause SLA, you can set status(es) in which you want to hold issue, and do not want to count time regarding SLA.


Select "Add/See JQL condition" from settings menu and paste your JQL.



If JQL definition has already been defined, image will be seen.
Same as JQL, if any "Paused Status" defined, image will be seen.

Overdue Transitions

With JEP 4.1.0 you can now define SLA for each transitions (status changes) in order to track overdue
It comes with a colored custom field which displays each overdue transitions



And also, if you add "JEP - Overdue Status" custom field to issue navigator, each issue that has at least one overdue, can be seen as red colored in issue navigator


You can also configure "Overdue" custom field in order to group/separate your SLAs. For instance you may group as "Customer SLAs", "Internal SLAs" and collect SLAs in separate custom fields.
To do so, just go to "Admin > Issues > Custom Fields" and click configure link as below



Then, click on 'Edit Including SLAs' link



Select SLA(s) which you want to see in the custom field



× Warning! It is strongly recommended that you select only one SLA per "Time to SLA" and "Overdue Status" custom fields, if you want to use this field in JQL statements.
After saving SLAs, reindex (Admin > System > Indexing > Re-index) JIRA in order to take effect


Time to SLA custom field

Calculates remaining time by defined SLA for current status

If defined an SLA for transition (20 minutes for Open to Resolved for critical issues as below)



then JEP - Time To SLA custom field calculates and counts down remaining time for this SLA. If expanded, SLA value, last status change date and SLA overdue (if has) can be seen as well.
It has been colored (since 4.5.0 version) according to deadline: green (more than one days), yellow (time is ticking) and red (overdue).



You can also watch screencast about JEP - Time To SLA and JEP - Overdue Status custom fields

If you want to define your SLAs under additional condition(s), you can define using JQL as below :

You can also pause your SLAs when the issue is within specified statuses

Just like 'Overdue' custom field, you can configure 'Time to SLA' custom field to group/separate SLAs that you want.



SLA Indicator custom field

Detects all (JEP) SLA custom fields and shows whether issue met SLA or not so far.

Typically it shows MET or NOT MET like status lozenges
If the issue breaches SLAs, it shows "NOT MET", and a dialog (seen as below) will be visible upon.



You can use this field to filter issues using JQL. Same visual SLA Indicator may be seen on Issue Navigator as well.

Searching against SLA fields

You can use SLA custom fields in your JQL statements. Also, plugin comes with two handy JQL functions: slaStillHaveTimeIssues() and slaOverdueIssues()

slaStillHaveTimeIssues() and slaOverdueIssues() JQL functions

slaStillHaveTimeIssues() function does not get any parameters and returns all issues that still have time to SLA

slaOverdueIssues() function does not get any parameters and returns all issues if they breach at least one SLA definitions



× Warning! Defining separate "Time to SLA" custom fields per SLA will help getting accurate results.

Time to SLA field in JQL

To filter issues against "Time to SLA" field, begin typing the name of the custom field and click on checkbox



You will see input pop up, the values will be relative to the current time. For instance if you type 0 into "(greater than)" field, that will filter and list the issues that have at least 0 seconds to SLA.



Overdue field in JQL

To filter issues against "Overdue Status" field, begin typing the name of the custom field and click on checkbox



Within upcoming pop up, enter your time string to filter issues by their "overdue".



SLA Indicator in JQL

If you prefer to filter issues whether they met SLA conditions or not, add SLA Indicator to your JQL query browser



Type "MET" or "EXCEEDED" (or your defined string if you changed it in custom field configuration page)



Reopening counter

You may see a counter of all reopening actions of issue. You may also search for issues according to this counter as well

You can define and configure your own counter fields easily. Just select custom field type and give a name. If you select "Customisable counter custom field type", you can also select your own status to be counted.
If you choose 'Field Change Counter' you can see the field which counts how many times the configured field/custom field has been changed so far.

Comment custom field

What a shame that JIRA does not have any comment field in issue navigator, so that we can have a look at our issues with initial or latest comments.


Luckily, Enhancer Plugin has a brand new Comment custom field. You can easily define and configure this field.



  • Name: The name of the custom field (This name will be displayed in screens and you will use this within JQL)
  • First/Last: You want custom field to show first or last comment
  • Max Length: For some reason you may want to trim comment length.
  • Only public comments: You may want to display only public comments, not the pricate ones.
  • Show user: Add commenter user's display name to comment field
  • Show timestamp: Add the creation date info to the field
  • Renderer type: If you do not want to see formatted text, you can change it here

Also you can see our demo on comment field usage and customization. Below, you can see demo.

Linked Issues custom field

JEP Linked Issues custom field displays the number of linked (with specified link type) issues. And it is searchable: e.g. you can find issues which have more than 3 linked issues with 'causes' issue link type.

Go to JIRA > Admin > Addons > JEP Menu > Custom Field Configuration and click on "Add new Linked Issues custom field" button.





Name your field, select issue link type and add "Add custom field" button. That's it.




After reindexing JIRA, you can use this field in searching



Available since JEP 4.25.0 for JIRA 6.x or JEP 5.13.0 for JIRA 7.x

Reopenings tab panel

In an issue view, you may find "Reopenings History"

Stateoscope tab panel

Vivid and clarified issue state change history

SLA Overview tab panel

SLA Overview is a very handy panel in which you can see all (passed or waiting) SLA activities.

Red, Yellow and Green bullets indicate SLA Overdue, SLA In Progress and SLA Met.
And also you can find total working duration and paused duration as well.

Workflow conditions

Enhancer Plugin for JIRA comes with two additional workflow conditions. Previous Status Condition and Check User in Custom Field Condition


If you click Add button within a workflow transition's conditions tab you will see these JEP conditions as below







Check user in custom field condition

Select JEP - Check user in custom field condition and configure required parameters





Then, your condition will be in action







Previous status condition

Select JEP - Previous status condition and configure required parameters





In this condition, it is configurable to check either just the previous status, or any time that issue has been set to specified status.



You can also see the screencast here




Parent issue JQL condition

Select JEP - Parent Issue JQL condition and specify the JQL that should be matched for parent issue in order to display transition.





If parent issue matches given JQL then the relevant transition link will be displayed to the user

Workflow validators



Field has been set validator

Select JEP - Field has been set validator





and configure required field parameter





Then, your condition will be in action





If defined field has not been set before transition, an error as below will be fired.





Parent issue status validator

Sub-issue's workflow transition can be prevented according to parent issue's status. For instance, it can be configured that no sub-task can be created unless parent issue is in status of 'Open' or 'In Progress'











User in project role validator

Issue's workflow transition can be prevented unless the user is in specified project role(s)





Parent issue JQL validator





If parent issue does not match given JQL, the specified error message will be displayed to user.

Post functions

If you click Add button within a workflow transition's you will see JEP workflow post functions (starred as below)


Assign to a User in a Role post function.


Configure required parameter


Whenever issue's transition has happened, the issue will be assigned to a user in the specified role
It is configurable to assign the issue to a random user in the role or to user in the role that has been assignee of the issue before.
Please bear in mind that if you use this post function within "Create Issue Transition", post function should be placed right after "Creates the issue originally." statement.
You can also see the screencast here





Assign to a user in a role, based on a field of issue post function

Assign to a user in a role, based on a field of issue post function assigns issue to a user within the specified role automatically, if your selected field matches the value entered.
Just select the role that the issue will be assigned to, select a field and enter the matching string. If the value of the field matches with the value you defined the issue will be assigned.
For instance, you can define a post function to assign issues automatically to the "Critical users" role within the transition "Start Progress", if the priority of the issue is critical.



You can also see the screencast here





Notify overdue transition post function

Another post function comes up with plugin is the Notify overdue transition post function
You can add this post function with time limit (as minutes) parameter, in order to create a notification per each transition that has an overdue. Email templates can be created or modified according to each transition. Email will be sent to members of specified role.



This is the view that already created post function



Notify when a field has been set within the transition post function



This post function can be used to notify specified role by email, when a field has been set within the transition.





Assign issue to the user in custom field post function


Automatically assigns the issue to the user that is stored within the selected user custom field. First, as an example to assign issue to "Last In Progress User", select the custom field.




Post function will be seen as below:




After publishing workflow, the issues will be assigned accordingly within the transition.


Reports and gadgets

From version 4.4.0 on, JEP (Enhancer Plugin) provides handy report gadgets. To add JEP gadgets into your dashboard, -under your dashboard- click Add Gadget button, and type JEP in order to filter JEP gadgets.
Select gadget(s) to see in your dashboard



Time Between Gadget


Displays time(s) elapsed between transitions, (e.g Time Between Open - In Progress, In Progress - Resolved, and Resolved - Closed)



To use this gadget, you need to define Time Between custom fields.
Configure your gadget accordingly



Averaged Time Between Gadget


Displays averaged time (weekly or monthly) between transitions, (e.g In Progress - Resolved). For instance you can see average time passed between In Progress to Resolved monthly or weekly.



To use this gadget, you need to define Time Between custom field.
And configure your gadget accordingly




User/Group History Report and Gadget

  • Go to "reports" section and find User/Group History Report link and click, criterias page is as below







  • Fill the criterias and press 'Next' button to see results.



From version 4.4.0 on, User/Group History Report is now in your dashboard, with more configuration options.




You can configure the gadget as follows



Status counter gadget

To use this gadget, you need to define Counter custom fields.
After defining custom fields, and configuring accordingly, here is the gadget view :

And the configuration page:



Total Resolutions per User Bar Chart

This handy gadget displays resolution counts per user against your filter.
Gadget automatically creates "Last Resolved User" custom field if not defined before.

And the configuration page:



Top Users Gadget

This gadget displays 'Hall of Fame' user list by selected JEP user customfields.
For instance you can configure gadget, by any of your favorite filter, and any JEP user custom field (Closed User, Resolved User, etc..) as below



Then the result will look like



Two Dimensional Filter Gadget

Built-in JIRA "Two Dimensional Filter Statistics" gadget does not support some custom fields.
But now, you've got JEP customized Two Dimensional Filter Gadget which supports JEP 'User' and 'Date custom fields.
You can configure it to display daily/weekly or monthly cumulated



Then the result will look like



Time passed till first response bar chart gadget

JIRA's built-in first response time gadget does not take working hour into account, JEP's first response time gadget does.
Configure gadget
  • Pick your favorite filter/project
  • Select period, how do you want to group results? Daily, weekly, monthly or yearly? Or you can select "Issue" to view by issues in y-axis.
  • Select "JEP Response Time" customfield you defined before. Here is the details on creating JEP - Response Time custom field"
  • Time interval can be second, minute, hour, day. y-axis will be displayed according to this parameter.
  • If you want to automatically refresh the gadget results, select appropriate "Refresh Interval"




Here is the sample result. It shows average response time as hours, grouped by month. On mouse over, it shows total issue number and when each bar is clicked, navigated to "Issue Navigator" showing those issues.

Resolution Time Bar Chart Gadget

Similar to JIRA's built-in resolution time gadget, but with working calendar, average time grouped by week/month, and a couple of additional features.
Configure gadget
  • Pick your favorite filter/project
  • Select period, how do you want to group results? Daily, weekly, monthly or yearly? Or you can select "Issue" to view by issues in y-axis.
  • Select "JEP Resolution Time" customfield, if you did not already just click "Create now" link next to drop-down.
  • Time interval can be second, minute, hour, day. y-axis will be displayed according to this parameter.
  • If you want to automatically refresh the gadget results, select appropriate "Refresh Interval"




Here is the sample result. It shows average resolution time as hours, grouped by month. On mouse over, it shows total issue number and when each bar is clicked, navigated to "Issue Navigator" showing those issues.

Time In Status Gadget

Displays total/average time spent in specified status according to the company's working calendar. (Since 4.19.0 for JIRA 6 / 5.7.0 for JIRA 7)
Configure gadget
  • Pick your favorite filter/project
  • Select status you want to see time spent or average time
  • Select working calendar.
  • If you want to re-filter against latest issues, you can type a number corresponding to the days that issue was created before today
  • If you wish, you can give a custom name to gadget
  • Select mode whether you want to display user details or not
  • If you want to automatically refresh the gadget results, select appropriate "Refresh Interval"




Here is the sample result.

Resolutions vs Reopenings Gadget

Displays how many issues have been resolved and how many of them are reopened back grouped by JIRA users. Configure gadget
  • Pick your favorite filter/project
  • If you wish, you can give a custom name to gadget
  • Filter against creation date by entering a number in 'Days previously' field
  • If you want to automatically refresh the gadget results, select appropriate "Refresh Interval"




Here is the sample result.

Resolutions vs Linked Issues Gadget

Displays how many issues have been resolved grouped by users and how many related issues have been raised. This is useful when you raise separate bug issues for resolved issues. Configure gadget
  • Pick your favorite filter/project
  • If you wish, you can give a custom name to gadget
  • Filter against creation date by entering a number in 'Days previously' field
  • Pick issue link type
  • If you want to automatically refresh the gadget results, select appropriate "Refresh Interval"




Here is the sample result.

User Performance gadget

Displays valuable metrics (resolutions count, original estimation, time duration, reopenings, linked issues) per user by given filter. Configure gadget
  • Pick your favorite filter/project
  • If you wish, you can give a custom name to gadget
  • Filter against creation date by entering a number in 'Days previously' field
  • Enable 'Include estimate field?' if you want to see calculation of 'Original Estimate' field
  • 'Resolved user field' should be defined (before) and selected here in order to see user statistics
  • 'Time Between field' should be defined (before) and selected here in order to see overall and average time passed between selected events
  • 'Linked issues field' should be defined (before) and selected here in order to see sum of linked issues
  • 'Reopening Counter field' should be defined (before) and selected here in order to see the sum of reopenings of those resolved issues
  • If you want to automatically refresh the gadget results, select appropriate "Refresh Interval"




Here is the sample result.

Main Task Field Distributions pie chart gadget

Displays a pie chart grouped by the main task fields (or custom fields) with given filters which return subtasks. It reports as a pie chart according to fields (or custom fields) in parent issues for the subtasks which are given with filter.
Configure gadget
  • Pick your favorite filter/project
  • If you wish, you can give a custom name to gadget
  • Either select a custom field
  • Or select a JIRA field
  • If you want to automatically refresh the gadget results, select appropriate "Refresh Interval"




Here is the sample result.

Main Task Field Distributions bar chart gadget

Displays a bar chart grouped by the main task fields (or custom fields) with given filters which return subtasks. It reports as a bar chart according to fields (or custom fields) in parent issues for the subtasks which are given with filter.
Configuration of the gadget is same as above (Main Task Field Distributions pie chart) gadget
  • Pick your favorite filter/project
  • If you wish, you can give a custom name to gadget
  • Either select a custom field
  • Or select a JIRA field
  • If you want to automatically refresh the gadget results, select appropriate "Refresh Interval"


Here is the sample result.



JQL Functions

1jep.subTasksByFieldInMainTask returns subtasks of parent issues which have field-name = field-value equality

Some samples:
								issue in jep.subTasksByFieldInMainTask("assignee", "tdirk") 
						        issue in jep.subTasksByFieldInMainTask("component", "web")
						        issue in jep.subTasksByFieldInMainTask("fixVersion", "3.0")
						        issue in jep.subTasksByFieldInMainTask("issuetype", "Bug")
						        issue in jep.subTasksByFieldInMainTask("priority", "Highest")
						        issue in jep.subTasksByFieldInMainTask("resolution", "Unresolved")
2jep.subTasksByCustomFieldInMainTask returns subtasks of parent issues which have cf-name = cf-value equality
Only text, select and multi-select custom fields can be searched!

Sample:
								issue in jep.subTasksByCustomFieldInMainTask("Department", "Software")


Rest services

Time between field REST service

REST service that returns all 'Time Between field' info.
MethodGET
URL JIRA_BASE_URL/rest/jep-api/latest/customfields/timebetween/{customfield_id}?issue={issuekey}
{customfield_id} is the ID of Time Between custom field (e.g. customfield_11300)
{issuekey} is the id of issue (e.g. NP-132)
Possible success response
										{
											{
										  		"totalDurationAsMillis": 80000,
											  	"totalPausedDurationAsMillis": 0,
												"totalWorkingDurationAsMillis": 80000,
												"totalWorkingDurationAsFormattedString": "1 minute, 20 seconds",
												"executions": [
												{
													"startTime": 1393410407981,
													"endTime": 1393410488776,
													"fromStatus": "1",
													"fromStatusString": "Open",
													"toStatus": "5",
													"toStatusString": "Resolved",
										   			"totalDuration": 80000,
										   			"totalWorkingDuration": 80000,
										   			"totalPausedDuration": 0
												}
												]
											}
										}
										
Possible fail responses
{"success":false,"message":"No custom field found with id: customfield_12999"}
{"success":false,"message":"Custom field 'SLA Overview' is not of type Time Between Custom Field"}
{"success":false,"message":"issue parameter can not be empty"}
{"success":false,"message":"No issue found with key: {issuekey} "}
Available since JEP 4.16.0 for JIRA 6.x or JEP 5.4.0 for JIRA 7.x

Creating 'Time between field' REST service

REST service that creates 'Time Between' custom field.
MethodPOST
URL JIRA_BASE_URL/rest/rest/jep-api/latest/customfields/timebetween
POST data
	                       					{
											  "name": "Name of the field",
											  "event1": "STATUS", // possible values: STATUS, RESOLUTION, REOPENING
											  "status1": "1",		// Id value of the status	
											  "event2": "RESOLUTION",	
											  "status2": "",		// If STATUS is not selected, this field is not important
											  "occurrenceType": "CUMULATIVE",	// possible values: FIRST, LAST, CUMULATIVE
											  "workingTimeId": 0,				// 0 for 7x24, otherwise calendar Id
											  "formatterType": "true_true_true_true_true_true_true",	// suffix, month, week, day, hour, minute, second 
											  "pauses": [1, 2, 3]	// Paused (Frozen) Status Id values
											}
	                       				
Possible success response
										{"success":true,"message":"12008","code":12008} // Customfield Id value for the custom field
										
Available since JEP 4.22.0 for JIRA 6.x or JEP 5.10.0 for JIRA 7.x

Listing 'Linked Issues' custom fields REST service

REST service that lists all 'Linked Issues' custom field.
MethodGET
URL JIRA_BASE_URL/rest/rest/jep-api/latest/customfields/linkedissues
Possible success response
										[
											{
												"name":"Linked Issue 1", "customFieldId":12040, "issueLinkTypeId":10000, 
												"issueLinkTypeName":"Blocks","customFieldTypeName":"JEP - Linked Issues"
											},
											{
												"name":"Linked Issue 2", "customFieldId":12041, "issueLinkTypeId":10001, 
												"issueLinkTypeName":"Blocks","customFieldTypeName":"JEP - Linked Issues"
											}
										]
										
Available since JEP 4.25.0 for JIRA 6.x or JEP 5.13.0 for JIRA 7.x

Showing 'Linked Issues' custom field REST service

REST service that shows 'Linked Issues' custom field by given custom field Id.
MethodGET
URL JIRA_BASE_URL/rest/rest/jep-api/latest/customfields/linkedissues/{customFieldId}
Possible success response
										{
											"name":"Blocked Issues", "customFieldId":12040, "issueLinkTypeId":10000, 
											"issueLinkTypeName":"Blocks","customFieldTypeName":"JEP - Linked Issues"
										}
										
Available since JEP 4.25.0 for JIRA 6.x or JEP 5.13.0 for JIRA 7.x

Saving/Updating 'Linked Issues' custom field REST service

REST service that saves or updates 'Linked Issues' custom field
MethodPUT
URL JIRA_BASE_URL/rest/rest/jep-api/latest/customfields/linkedissues
PUT json data
	                       					{
											  "name": "Name of the field",
											  "customFieldId": 12010, // fill this attribute if you want to update existing, otherwise comment out this line
											  "issueLinkTypeId": "10001" // Issue Link Type Id	
											}
	                       				
Possible success response
										{
											"success": true,
											"message": "Field created, id: 12045",
											"code": 12045
										}
										
Available since JEP 4.25.0 for JIRA 6.x or JEP 5.13.0 for JIRA 7.x

Deleting 'Linked Issues' custom field REST service

REST service that deletes 'Linked Issues' custom field by given customFieldId.
MethodDELETE
URL JIRA_BASE_URL/rest/rest/jep-api/latest/customfields/linkedissues/{customFildId}
Possible success response
										{"success": true, "message": "", "code": 0}
										
Available since JEP 4.25.0 for JIRA 6.x or JEP 5.13.0 for JIRA 7.x

Deleting all 'Linked Issues' custom fields REST service

REST service that deletes all 'Linked Issues' custom fields.
MethodDELETE
URL JIRA_BASE_URL/rest/rest/jep-api/latest/customfields/linkedissues
Possible success response
										{"success": true, "message": "", "code": 0}
										
Available since JEP 4.25.0 for JIRA 6.x or JEP 5.13.0 for JIRA 7.x