Managing versions across projects
A common use case with Jira Software projects is to have a public-facing project where your customers can log defects and feature requests against released software, and an internal project that is used by the development team to track their work.
Having this setup allows teams to triage incoming requests and select relevant issues to work on without clogging up their actual project with thousands of issues.
However, realizing the benefits from this setup requires that the software versions in both projects are synchronized, allowing customers to report issues against the correct versions of the released software.
In this section, we will explore how to use automation rules to manage the version synchronization between projects.
To do this, we will need to ensure that when we release a version in the internal project, we create a corresponding version in the public-facing project that customers can then use when reporting bugs or creating...
