You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello Atlassian Community!
Each month, we run a series of Spotlights to highlight Marketplace vendors and apps that our team thinks this Community would find valuable. In last month's Spotlight on Appfire, we looked at different bug tracking tips to streamline your process.
This month, our Spotlight is on our friends at Rollout - a feature management solution taking big strides in product development.
Rollout is a feature management solution that gives engineering and product teams the most effective way to roll out new features to the right audience while protecting customers from bugs. They allow teams to gradually roll out new features to subsets of their users to ensure which can allow them to test for bugs and measure results.
Now that Rollout has rolled out (excuse the pun) with an integration for Jira Cloud, users of the app can now view feature flag information from a Jira issue. This allows for continuous visibility for issues, even past production! Users can understand what's happening in production and use that information to create a feedback loop that will help guide future product decisions.
We'll just name drop a few here:
How do you know when an issue is done? And I mean done-done? Rollout raises the issue of how to close the issue management loop in our latest vendor guest blog. A common problem experienced by developers, marking an issue as 'done' can later haunt their day when that issue is revived from the dead 👻.
Now with the Jira integration with feature flags, developers can turn on changes to specific users to monitor the issue before rolling out the fix to everyone. We can hold off on labeling an issue as 'done' until it has passed a whole series of production checkpoints where the team can monitor it at every step of the way. Once it's passed all these steps, we can finally feel confident enough to label an issue 'done'.
Not everyone uses the same method of deciding when an issue is done. Drop us a comment below to let us know how your team decides when to label an issue 'done'!