I wanted to ask how do you manage Versions in multi-product Service Desk?
For example we use in Support Service Desk multiple products as follows:
ProductA
ProductB
Logically if we add just versions 15.1 and 16.1 into Version configuration, reporting and versioning control provided by Jira will be inaccurate, because we don't know for which product the issue was raised for.
To solve this problem, I started using Version as "Product + Version".
For Example:
This seems to work fine with reporting and also customers/users can select Product and Version in Affects Version or Fix Version fields.
The problem is that if engineering uses standard Jira Software projects where a project represents a Product, they often use use just the version in version field. This means we are not in sync and automated updates are not possible. I requested engineering to update their versions and include the product in the version, that we can stay in sync.
This seems to work, but some people don't like it because the version is not simple version, but needs to include the product.
How do you go around this problem?
Join us June 26, 11am PT for a webinar with Atlassian Champion Robert Hean & Loom’s Brittany Soinski. Hear tips, stories, and get your burning questions answered. Learn how Loom makes training and enablement easier. Don’t miss it!
Register todayOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.