Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Keeping your sanity as an Atlassian Product Owner


I will be speaking at a Czech Jira conference in February about the topic of Jira+Confluence Maintenance. One of the subtopics I would like to tackle is "Keeping your sanity as the Atlassian Product Owner". In it, I would like to cover the best practices about maintaining Atlassian tools in a corporate environment, standardization, documentation and how to deal with terrible requests.

I would like to ask you about your experiences with being an Atlassian product owner - what are the do's and don'ts. Could you please share your stories with me here for inspiration?


Thank you!


1 comment

Mirek Community Leader Jan 20, 2020

One of the biggest problems in maintaining Jira/Confluence are .. addons. There are too many of them with different support and safety.  If those are no specific rules which addons can be installed and when it would be a complete mess. Handling maintenance of an instance where people keep asking for new things is very hard. Especially if things are free and not having much arguments to deny such a requests. Product Owners should be ready to deal with addon requests in a good way. If you are too open you can end up with 40 addons where in one or two years half of then would not be used or forgotten but if you want to remove you notice that some projects or spaces are are still using them and removing something now could be a problem...

Second thing that might be a pain .. customization. Of course something is possible via script or other hack but think about maintenance, upgrades later.. Depends of course how big the customization is but overall avoid changing much if this is not really affecting everyone..

Other good decision of the Product Owner is to stick with Enterprise Releases even if that mean no super new cool features for a half of the year after release (in latest version). That is very useful when you need to do a quick upgrade when there is a bug or security issue.. No need to do all the user tests, addons and customization should be still working.. It would save a lot of time.

Everything of course depends on the size of the instance but overall above rules are good for everyone unless someone do not really care what would happen in the future.

Like Kamil Beer likes this

Very true. Thanks for your insightful reply!


Log in or Sign up to comment
Community showcase
Posted in Teamwork

What questions/topics do you have on organizational transformation?

Atlassian is looking for your questions on organizational transformation. We often talk about issues that affect our immediate teams or share best practices on relationship management. But, we ...

230 views 5 6
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you