Jira/Confluence Configuration Management Best Practices

Has anyone developed a configuration management guide, set of policies and practices, or other type of documentation for maintaining Jira and/or Confluence? What I'm interested in are practices around making changes to Jira/Confluence itself -- things like handling change requests (new fields, new projects, new workflows, etc.), plugin installation requests, issue deletion, upgrades, and the like. I'm wondering what policies you have for request review, testing of changes, migration of changes from Stage to Production, etc.

If you have developed any material like this that you are willing to share, I would appreciate it. Just looking for something that works for you which I could review as a starting point for our own policies. Thank you.

1 answer

This widget could not be displayed.
Timothy Chin Community Champion Jul 22, 2013

Well, you can use JIRA itself to manage all of these request. Firstly, you will have to determine the business process and build it into your own JIRA. Create a new project and configurations that you need.

Then, document these information down in a new Confluence Space.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

112 views 1 2
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you