Pre-populate Jira Service Desk Descriptions based on Request Type

David Yu
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 29, 2019

Thought I'd share this neat trick with Jira Service Desk + Script Runner.

I think most people already use Script Runner Behaviors as a way to pre-fill a form with default text in the Description.

This is useful for times when you don't really want to add yet another field, and simply want to prompt or guide the user to give you the necessary information to complete the task.

While configuring Script Runner to do this on a per request is simple enough, what I wanted to was to give the power the end-users so they can configure the form themselves without admin intervention.

So here's how it works.

1. The user edits their Service Desk Request's Form Help section. They simply precede the field-help with a question mark to indicate this is a "guided field."

Selection_120.png

2. The form when presented to end-users will look like this:

Selection_122.png

 

Users now have full control of what to prompt the user for, and it's available to every Service Desk. Will include Script Runner script in reply to make this post cleaner.

1 answer

0 votes
David Yu
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 29, 2019

Snippet example of the behaviours script: https://bitbucket.org/snippets/superoni/eaGobL

It just inspects the Form Help, and parses it into the Description box.

When creating your Behaviours configuration, apply to All Service Desk. In initialiser, save the snippet to file, and provide path to file. Specify 'run' under 'Enter the name of the method to execute.'

Let me know how you like it. Tested on Jira 7.X.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events