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.
So, for our company, we were experimenting with capturing a significant amount of information in a JIRA ticket (we're using Cloud) for incident management (ie a call comes in, it's researched, tested, reviewed, risk-rated, approved, etc).
In that scenario, we have added rather a large number of custom fields to capture all these reviews and their feedback, and to keep things clean, I put them into tabs within the Issue View/Edit configurations.
But now -with the new issue view - there are now tabs, and that list of custom fields stretches a mile long on the right edge.
Thoughts? How can one organize things like this in the new style?
For us, seems like removing those tabs is a big negative.