Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
JIRA Development Cookbook

You're reading from   JIRA Development Cookbook Develop and customize plugins, program workflows, work on custom fields, master JQL functions, and more to effectively customize, manage, and extend JIRA

Arrow left icon
Product type Paperback
Published in Nov 2011
Publisher Packt
ISBN-13 9781849681803
Length 476 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Jobin Kuruvilla Jobin Kuruvilla
Author Profile Icon Jobin Kuruvilla
Jobin Kuruvilla
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

JIRA Development Cookbook
Credits
About the Author
Acknowledgment
About the Reviewers
www.PacktPub.com
Preface
1. Plugin Development Process FREE CHAPTER 2. Understanding Plugin Framework 3. Working with Custom Fields 4. Programming Workflows 5. Gadgets and Reporting in JIRA 6. The Power of JIRA Searching 7. Programming Issues 8. Customizing the UI 9. Remote Access to JIRA 10. Dealing with a Database 11. Useful Recipes Index

Jelly escalation


Before winding up this chapter, let us have a quick look at how we can use one of the useful features of JIRA to escalate inactive issues by transitioning them to a pre-defined workflow status.

Jelly Service is a built-in service in JIRA using which we can run useful Jelly scripts at regular intervals. Atlassian explains in its documentation at http://confluence.atlassian.com/display/JIRA/Jelly+Escalation about running a Jelly script to move issues that were not updated in the last seven days to an inactive status.

Let us have a look at this recipe at how to modify the script and transition issues in to different workflow statuses.

Getting ready

Make sure Jelly is turned on in your JIRA instance. It is disabled by default due to security concerns. You can turn it ON by setting the jira.jelly.on property to true.

You can set the property by adding -Djira.jelly.on=true into the JAVA_OPTS variable. Adding this variable depends on the server and operating system.

For example, the...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image