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,462,647
Community Members
 
Community Events
176
Community Groups

What is the most recommended way to test Jira customizations (workflow / custom fields)?

Assuming that you have a PROD instance and a STAGE instance that isn't always 100% a copy of PROD due to data growth and your Jira is running on out-of-the-box settings.

You're tasked to come up with different workflow (s) and custom fields to meet new business requirements and want to be able to efficiently conduct testing without potentially running into in catastrophic (e.g Jira crashing or causing irreversible DB changes).  Would you:

1) Do absolutely everything in STAGE first, which includes:

  • Create a test project
  • Set up unique workflow/screen schemes
  • Design and test functionalities
  • Conduct the UAT there with stakeholders to make sure requirements are met
  • Then, manually repeat all of the steps above in PROD instance (while workflows are exportable, they do not usually go into Jira PROD correctly if certain

2) Do the tasks with minimal risks in a TEST project in PROD instance, which includes:

  • Create a test project with restricted permission scheme to only allow minimum users to see
  • Set up unique workflow/field schemes
  • Design and test functionalities
  • Conduct the UAT there with stakeholders to make sure requirements are met
  • Then, "flip the switch" by switching the workflow / screen schemes with "live" project and keep the "old" schemes around for potential rollbacks.

Would love to hear how my fellow Jira admins work their magic!

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events