Summary

In this chapter, we learned how we can use automation rules to minimize the administrative overhead usually involved in managing and working with Jira Software projects, and indeed these can be applied to most project types within Jira.

In particular, we learned how to keep versions synchronized across projects, which is especially useful when you have a software project spanning multiple Jira projects, whether they be internal team projects or, as in our example, public projects for customers to log and track requests.

Keeping hierarchies of issues in sync is a very common task faced in Jira projects and in this chapter, we learned how to use a looping rule to achieve this using the most common hierarchy encountered in Jira Software projects. Lastly, we learned how to maintain visibility of any scope changes to a sprint and how we can also use automation to adjust the scope of a sprint.

With the exception of the sprint-specific examples we have looked at, the topics...