nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Got feedback on release tracks?

Matt Tse

Hi everyone!

It's been a while. My apologies for not being more active in this group. Our teams have been heads down with planning and exploring ideas to improve our change management-related features.

We've received a great deal of feedback on the sandbox experience (thanks again to those who provided their input) and have our hands full planning the next few iterations. I'd like to use this discussion to shift gears a bit and focus on release tracks.

As a quick recap, release tracks determine when you and your users get Jira Software, Jira Service Management, and Confluence changes and new features. With release tracks, you’ll now have 3 release schedule options to choose from - continuous, bundled, and preview (for sandboxes only).

A few questions that I'd like to ask the group:

Are you using release tracks today?
1. If you are, what do you like about it?
2. If you aren't, why not?
What could make the release tracks a better experience for you?

Thanks so much in advance! Looking forward to hearing from you all.

Cheers,

Matt

Comments

Dave LIAO

@Matt Tse - hey Matt!

I'm not personally using release tracks, but I've heard that the current release track offerings aren't clearly explained enough (I read the descriptions of the three current track options and agree), and aren't long enough (4-6 weeks isn't enough for some institutions).

Bundled and Preview seem to have a relationship, so I'd figure they should be next to each other in the table.

Matt Tse

Thanks for the feedback Dave! Could you tell me more about what's not clear in the documentation? How can we make it easier to understand?

Totally hear you on the timeframe. Can you help me understand what scenarios would require a lengthier cycle? I'm familiar with some of the regulatory reasons such as those who work in the health care / medical device sectors.

Cheers,

Matt

Jack Brickey

This really should be part of standard as well. If you simply look at it holistically from a product perspective it makes a lot of sense. Not everything should be about driving individuals to premium for the added revenue. I may simply not be understanding the added cost of such a feature. So maybe that added cost if any would explain why premium.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

migration

change

release

change-management