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, aafp, jira migration, marketing collaboration, end siloed work, streamline workflows, kerrie gottschalk, jira cloud admins, unified marketing, process visibility, team efficiency, cross-team collaboration

How Kerrie Gottschalk unified AAFP’s marketing team with Jira

At the American Academy of Family Physicians, siloed marketing teams faced delays and duplicate work. Kerrie Gottschalk shook things up by moving the department to Jira, streamlining processes, boosting visibility, and sparking stronger collaboration.

Read the story
AUG Leaders

Atlassian Community Events