Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Thanks! And follow up question


Hello everyone,

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,


1 comment

Which event was this?

And out of curiosity, what is it you are looking to perform version control on?

The event was '5 Jira System Field Pitfalls (and How to Avoid Them)’ (hour-long webinar).


Looking to version-control any Jira configuration settings and contents except Personal / Company identifiable data (so general settings for all projects not specific project settings).  Settings such as global issue statuses, workflows settings, resolutions, and priorities.   Kind of what happens already when exporting data like Users and user group settings ( but geared to Jira Cloud settings like the ones mentioned above (and maybe even system-generic JQLs).  Also be able to share these settings by cloning, branching, and creating pull requests among Jira admins. 
This would enable reverting to a previous instance of settings after falling in the pitfalls mentioned in the 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.


Log in or Sign up to comment

Atlassian Community Events