Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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
4,551,979
Community Members
 
Community Events
184
Community Groups

Thanks! And follow up question

Edited

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,

Andy

1 comment

Rob Horan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jul 20, 2022

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 (https://support.atlassian.com/jira-cloud-administration/docs/export-issues/) 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.
Rob Horan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jul 20, 2022 • edited

That would mean having the ability to export settings.

Whaddya want, the ability to rename groups too?  :)

https://jira.atlassian.com/browse/ID-6677

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.

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events