-
Suggestion
-
Resolution: Unresolved
-
15
-
Issue Summary
Description fields in Jira Align do not have product-wide format & behavior standardization, in the Stories, Defects, Acceptance Criteria, Features, Capabilities, Epics, Dependencies and Objectives.
The description fields show different behaviors in the work items listed above depending on whether it has rich-text support, whether it has auto-save functionality, whether it shows the formatting toolbox and whether it is integrated / non-integrated.
In terms of overall product consistency, these cause problems and create user dissatisfaction.
Steps to Reproduce
- Log in to Jira Align
- Go to Stories, Defects, Acceptance Criteria, Features, Capabilities, Epics,Dependencies and Objectives work items
- Check the following items on the description field behaviors, while the program/portfolio is integrated OR non-integrated:
- whether it has rich-text support,
- whether it has auto-save functionality,
- whether it shows the formatting toolbox
- whether there is an eye icon.
Expected Results
Seeing consistent and standard behavior on the description fields, with the auto-save feature, rich-text support, and format toolbar.
Actual Results
The product shows very inconsistent description field behavior in this regard.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
ALIGNSP-20410 Loading...
-
ALIGNSP-27295 Loading...
- is reviewing
-
ALIGNSP-20792 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- resolves
-
ACE-3852 Loading...
-
ACE-3855 Loading...
-
ALIGNSP-15250 Loading...
-
ALIGNSP-15307 Loading...
-
ALIGNSP-17303 Loading...
-
ALIGNSP-24229 Loading...
-
ALIGNSP-26854 Loading...