Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,539
Community Members
 
Community Events
184
Community Groups

Looking for release management ideas and best practices

I'm sure this has been covered numerous times, but I couldn't find any topics that seemed directly related - and I think I'm looking for some "real world input" as opposed to just "official best practices". 

Summary: We are a very small distributed team. I was brought on to implement project management/DevOps because the company previously had nothing but email. I have some formal project management experience, but Jira is "new" and the past year or two has just been spent setting up the platform/workflows/statuses/etc 

I recently started using Kanban boards & releases - but I'm having some issues managing releases "properly"

1. When all issues are marked "Done" - everything is fine. 

2. When most issues are marked "Done" - but some "To Do" items will not make it into the release by the deadline, I can just mass-move them into a new release - and everything is fine.

3. When we have several "In Progress" issues - I'm not sure how to best handle them.
I can manually move them to the new release, but this is somewhat tedious when I need to do this for 15-20 bugs/issues

I can move them into the 'To Do' column & mass move them to the next release, then move them back to "In Progress" - but again, this is tedious. 

Is there a way to move them into the new release but keep their current progress, without the manual effort? 

Additionally, I want to move towards more of a scrum methodology - but I can't get this team to estimate their own tasks, at all - and our boss has never made them/won't make them now; which means I'm doing the estimations. Any advice for coaxing a team to do this? 

Any other advice in general from small distributed teams? 

Thanks in advance!

1 comment

Manon Soubies-Camy _Modus Create_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 18, 2018

Hello Jordan,

Can't help you with the scrum part, but have you tried bulk change? You could update the Fix version or transition all of your issues at once.

Hope this helps,

- Manon

Somehow it hadn't occurred to me to just filter by version/status. 
This will work perfectly. 
Thanks.

Manon Soubies-Camy _Modus Create_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 18, 2018

Glad it helped! :)

Comment

Log in or Sign up to comment