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

0 votes
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
Published Nov 29, 2018 in Jira

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,098 views 0 8
Read article

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