Jira Product Discovery: Document field definitions
Document Jira Product Discovery field definitions by editing each custom field’s description, then calibrating the model against representative ideas.
A field name such as Impact is not enough to make scores comparable. Put the unit, scale and evidence standard where scorers can discover them instead of relying on a meeting explanation.
Step-by-step guide
Identify the ambiguous fields
Inspect a recent scoring discussion for conflicting interpretations. For example, Reach may mean users per month to one reviewer and accounts per quarter to another. Select one definition and record which unit the prioritization model actually needs.
Edit the custom field description
As a space admin, open Fields in a view, hover over the custom field and choose its edit control. Update the description with the unit, allowed interpretation and evidence source. Changes save automatically when editing the field information.
Add concrete anchors
For an Impact rating, write examples of the lowest and highest categories relevant to the product. For Confidence, state whether the input is a decimal or percentage. Link or document the associated formula so reviewers can see how a mistaken representation changes its output.
Calibrate and revisit existing scores
Have two reviewers score the same export-error idea using the new definition and compare their reasoning. Revisit older values that used another unit before treating the field as consistent. Preserve uncertainty instead of forcing every idea to have an apparently precise number.
Common mistakes
Renaming a field without reconciling values
A clearer label does not convert historical values into the new unit. Review the existing dataset before relying on its ranking.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.