Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Enforce Description Formatting Rules

BlaineHafner
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 27, 2019 edited

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!

1 answer

1 vote
JimCoulter2
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 27, 2019

I have the same issue! 

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, confluence, loom, atlassian intelligence, ai notes, ai-powered meeting notes, atlassian community events, ace, confluence ai, loom ai integration, ai note-taking, atlassian ai features, team '25, atlassian live learning, confluence automation

Unlock AI-powered meeting notes: Join our live learning session! 📹

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!
AUG Leaders

Atlassian Community Events