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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Thanks to the Atlassian team who put together this event, specially to the panelists, and also to everyone who attended and contributed!
My follow up question is:
Is Atlassian planning a version-control mechanism for Jira configuration(s)? It would be amazing if we could do this such as export it to a folder or set of folders that can be versioned and imported / cloned to another Jira instance (by using git or something alike - even using npm to start Jira projects configs from a CLI).
Thanks and regards,
The event was '5 Jira System Field Pitfalls (and How to Avoid Them)’ (hour-long webinar).
That would mean having the ability to export settings.
Whaddya want, the ability to rename groups too? :)
Fun fact, when that ticket was entered, In Da Club by 50 Cent was the hottest song, the invasion of Iraq was in full swing, and so was the SARS epidemic.
All jokes aside, exportable settings would be FANTASTIC for sharing settings across instances. I suspect there are so many variables to keep track of - too many options for customization and conflict.