Power Scripts Recipes

The scripts below are designed to provide examples of how Jira administrators can leverage Power Scripts to extend native Jira capabilities.

Page:

Add a group as participants in Jira Service Desk
Page:

Add internal comments to Jira Service Desk requests
Page:

Add participants automatically to new Jira Service Desk requests
Page:

Adjust an estimate according to assignee
Page:

Assign an issue while maintaining the user load
Page:

Assign issues automatically based on workload
Page:

Assign issues to the previous assignee
Page:

Assign users based on a decision table using SIL™
Page:

Automatically archive old projects
Page:

Automatically move unresolved issues to next sprint and update story points
Page:

Automatically update the custom field ID and/or name in filters
Page:

Calculate the due date based on custom field values
Page:

Compare two fields with custom JQL
Page:

Copy a custom field value to another field when changed
Page:

Copy data from the parent issue
Page:

Copy the reporter and watchers on duplicate issues
Page:

Copy watchers to sub-tasks
Page:

Copying rich formatted description or Atlassian Document Format (ADF) example
Page:

Create a clickable link disguised as a Power Action™
Page:

Create a custom cascading dropdown field
Page:

Create a Select All option in a dropdown list
Page:

Create a sub-task automatically based on custom field selection
Page:

Create a validator for a component lead
Page:

Create custom JQL functions for nested issue reporting
Page:

Create story subtasks and close them when story is closed
Page:

Disable inline edits
Page:

Display a message custom field based on a drop-down list value
Page:

Display all issues linked to a given issue and link type
Page:

Display all issues where work logged exceeded estimate
Page:

Ensure that issues have attachments
Page:

Filter based on multiple criteria by using a non-Boolean JQL function
Page:

Filter by project and issue type
Page:

Get the time spent by an issue in certain statuses
Page:

Hide fields for users with no developer role
Page:

Hide multiple fields based on custom field value
Page:

Hide specific issue types for certain users
Page:

Hide specific priorities for certain projects
Page:

Hide the comment field during a transition
Page:

Hide the Create issue button until an attachment is added
Page:

Hide time-tracking information
Page:

Initialize field values for a transition screen
Page:

Insight REST API
Page:

Limit possible resolutions based on issue type
Page:

Limit sub-tasks based on issue type
Page:

Limit the assignee to a specific group
Page:

Limit the issue type selection to specific users
Page:

Limit the number of characters in a text-entry field
Page:

Limit the number of user votes per month
Page:

Limit transitions based on the status of dependent issues
Page:

Make an issue read-only
Page:

Map story points to hours and automatically log work on completion
Page:

Perform searches with LDAP
Page:

Prepopulate fields during a transition
Page:

Prevent a select list from displaying certain options
Page:

Prevent a select list from displaying certain values
Page:

Replicate the native Jira email handler
Page:

Require fields in subtasks
Page:

Require the fix versions when resolving an issue
Page:

Require users to log work before transitioning an issue
Page:

Reset a field
Page:

Search for all issues associated with multiple epics
Page:

See and search on the last person to modify an issue
Page:

Set approver in Jira Service Desk
Page:

Set default values for system fields on the Create screen
Page:

Synchronize comments between projects
Page:

Track completion progress
Page:

Transition past due issues
Page:

Update Portfolio Parent Link using REST API
Page:

Use a workflow validator based on logged hours
Page:

Use validators based on date range