I currently work for an organization, that stores user stories within the "Acceptance Criteria" due to issues in the past with over-formatting & exporting JIRA based spreadsheets. We have displayed interest in shifting our user stories back to the description field, but would like to ensure we don't encounter the same problem as we did in the past.
Is there a best practice to enforce a formatting policy on the description field?
We're currently concerned as we're shifting from a local instance of JIRA to the cloud, and we're unsure how long we may be able to revert to the old view, before JIRA disables that functionality. As it is currently formatted, the Acceptance Criteria in mobile is tucked away on the right side of the screen, and cannot be incorporated into the Description column, which would maximize visibility.
Thanks!
I have the same issue!
Did you catch the news at Team ‘25? With Loom, Confluence, Atlassian Intelligence, & even Jira 👀, you won’t have to worry about taking meeting notes again… unless you want to. Join us to explore the beta & discover a new way to boost meeting productivity.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.