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
Welcome to the Atlassian Community!
Short answer is that you don't. There is no "export config settings" other than taking a complete backup, which is only then useful for creating a copy of the system.
What are you trying to achieve with your "export"? We can probably talk through options and tools to help you do it, but we can't until we know what you're doing!
An exported list is not going to help you much. It could well be obsolete within minutes of you exporting it. It's also clumsy and hard to search, because you'd be generating hundreds or thousands of lines of cross references.
You will find it a lot easier to focus and drill-down in the UI. For example, if you simply look at the list of workflows, you can immediately see which schemes are using each workflow, and you'll be able to drill-down into them without having to plugh through thousands of lines of text data. Similarly the workflow scheme list will tell you about projects and hence issue types using them.