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
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Automate Everyday Tasks in Jira

You're reading from   Automate Everyday Tasks in Jira A practical, no-code approach for Jira admins and power users to automate everyday processes

Arrow left icon
Product type Paperback
Published in Jan 2021
Publisher Packt
ISBN-13 9781800562868
Length 314 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Gareth Cantrell Gareth Cantrell
Author Profile Icon Gareth Cantrell
Gareth Cantrell
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Section 1: Getting Started – the Basics
2. Chapter 1: Key Concepts of Automation FREE CHAPTER 3. Chapter 2: Automating Jira Issues 4. Section 2: Beyond the Basics
5. Chapter 3: Enhancing Rules with Smart Values 6. Chapter 4: Sending Automated Notifications 7. Chapter 5: Working with External Systems 8. Section 3: Advanced Use Cases with Automation
9. Chapter 6: Automating Jira Service Management 10. Chapter 7: Automating Jira Software Projects 11. Chapter 8: Integrating with DevOps Tools 12. Chapter 9: Best Practices 13. Chapter 10: Troubleshooting Tips and Techniques 14. Chapter 11: Beyond Automation; an Introduction to Scripting 15. Other Books You May Enjoy

Using a checklist

When you are creating your rules, you are not always going to remember all the various points we have discussed in this chapter to ensure that your rules follow best practices.

Having a checklist that you can quickly reference can help in ensuring that you have followed both the best practices we have presented in this chapter and any organizational guidance you have prepared.

We have, therefore, put together a basic checklist that you can use as a starting point to create a checklist in the format that suits you best:

  • The rule is correctly scoped to only the project or projects that are affected.
  • The rule is documented and includes a business case and implementation approach.
  • The rule has been exported and stored in a version control system such as GitHub or Bitbucket.
  • An appropriate trigger was used, such as Field value changed rather than Issue updated.
  • The rule is using the most efficient conditions, such as the Issue fields condition...
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